Triple
T19471523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Giants 1900–1916 |
E487133
|
entity |
| Predicate | managerEnd |
P2941
|
FINISHED |
| Object | 1916 |
—
|
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: 1916 | Statement: [New York Giants 1900–1916, managerEnd, 1916]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managerEnd Context triple: [New York Giants 1900–1916, managerEnd, 1916]
-
A.
returnedAsManagerEnd
Indicates that an entity has ceased serving in a managerial role and has returned from a manager position at the specified end point or time.
-
B.
officeEnded
chosen
Indicates that a person’s term in an office or position has concluded at a specified time or under certain conditions.
-
C.
managerEnsures
Indicates that a manager takes responsibility to make sure a particular condition, task, or outcome is achieved or maintained.
-
D.
serviceEnded
Indicates that a previously active service or service relationship has come to an end.
-
E.
endEvent
Indicates that one event or process marks the termination or conclusion of another event or process.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633e8d9188190a4939f03bad89add |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7883308190b73912a71a35a835 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.