Triple
T20108609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Random—Burin—St. George’s |
E490263
|
entity |
| Predicate | representationEndedIn |
P113175
|
FINISHED |
| Object | 2010s |
—
|
LITERAL FINISHED |
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: 2010s | Statement: [Random—Burin—St. George’s, representationEndedIn, 2010s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representationEndedIn Context triple: [Random—Burin—St. George’s, representationEndedIn, 2010s]
-
A.
representationEnded
chosen
Indicates that a previously ongoing representation or acting-on-behalf-of relationship between entities has come to an end.
-
B.
endedWith
Indicates that one event, process, or state concluded with or was finalized by another specified event, condition, or outcome.
-
C.
alsoEnded
Indicates that one event or state concluded in addition to another already mentioned event or state.
-
D.
representedByEnd
Indicates that something is represented or characterized by its endpoint or final part.
-
E.
representationBegins
Indicates that the act or state of representing something starts or comes into effect at a particular point in time.
- F. None of above.
Provenance (3 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e666ddb09881909ad2aedd1e8a78da |
completed | April 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:28 p.m.