Triple
T24706947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stade de Reims team of the 1950s |
E611917
|
entity |
| Predicate | managerFrom |
P157014
|
FINISHED |
| Object | 1950 |
—
|
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: 1950 | Statement: [Stade de Reims team of the 1950s, managerFrom, 1950]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managerFrom Context triple: [Stade de Reims team of the 1950s, managerFrom, 1950]
-
A.
manager
Indicates that one entity holds a supervisory or administrative role with authority and responsibility over another entity.
-
B.
managementIs
Indicates that one entity holds a managerial role, responsibility, or authority over another entity.
-
C.
managerType
Indicates the specific category or role classification of a manager within an organizational or system context.
-
D.
manageThrough
Indicates that one entity exercises control, direction, or administration over another entity or process by means of an intermediary entity, channel, or mechanism.
-
E.
managementController
Indicates that one entity serves as the management controller responsible for overseeing, configuring, or administering another entity.
- 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_69e2c4d9c24c8190a3712d74327f0c6e |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
| PDg | Predicate description generation | batch_69f410fc18808190b4e47d5a71d3a126 |
completed | May 1, 2026, 2:33 a.m. |
Created at: April 18, 2026, 3:24 a.m.