Triple
T11215648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centrale |
E265431
|
entity |
| Predicate | alumniRole |
P97884
|
FINISHED |
| Object | leaders in industry |
—
|
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: leaders in industry | Statement: [Centrale, alumniRole, leaders in industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alumniRole Context triple: [Centrale, alumniRole, leaders in industry]
-
A.
hadAlumniRole
Indicates that an entity previously held a role or position as an alumnus/alumna of another entity (such as an institution or organization).
-
B.
campusRole
Indicates the specific position, function, or capacity an individual holds within a campus or academic institution.
-
C.
fieldAssociatedWithAlumnus
Indicates that a particular field of study, profession, or area of expertise is associated with or pursued by a given alumnus.
-
D.
hasAlumnusPosition
Indicates that an individual holds or has held a position or role as an alumnus of a particular institution or organization.
-
E.
hasAlumni
Indicates that an institution or organization is associated with individuals who formerly attended or graduated from it.
- 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8e8eef48190932a85784ce15c86 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfbbb188190861efd5d94fe27da |
completed | April 9, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69d77062271c8190b63da714ab5beff9 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:30 p.m.