Triple
T24701139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McKeen |
E611743
|
entity |
| Predicate | hasFirstRecordedRegion |
P157679
|
FINISHED |
| Object | Ireland |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Ireland | Statement: [McKeen, hasFirstRecordedRegion, Ireland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFirstRecordedRegion Context triple: [McKeen, hasFirstRecordedRegion, Ireland]
-
A.
hasActivityRegion
Indicates the geographic or spatial region within which an activity occurs or is applicable.
-
B.
hasRecordingHistory
Indicates that an entity has an associated record of past recordings or recorded events.
-
C.
hasRecordingWith
Indicates that one entity is associated with or includes a particular recording as part of its content or representation.
-
D.
hasRecordingLegacy
Indicates that an entity is associated with a historical or prior version of a recording, capturing its legacy or earlier state.
-
E.
hasMusicalRegion
Indicates a relationship where a musical work, performance, or element is associated with a specific geographic or cultural region in terms of style, origin, or influence.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e2c4d76d148190b58ad612467149a5 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
| PDg | Predicate description generation | batch_69f44a3adb7c8190941572f718b3b93c |
completed | May 1, 2026, 6:37 a.m. |
Created at: April 18, 2026, 3:22 a.m.