Triple
T23035896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FMS Delhi |
E573592
|
entity |
| Predicate | alumniType |
P150737
|
FINISHED |
| Object | corporate leaders |
—
|
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: corporate leaders | Statement: [FMS Delhi, alumniType, corporate leaders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alumniType Context triple: [FMS Delhi, alumniType, corporate leaders]
-
A.
alumniRole
Indicates that an entity holds or held a specific role, position, or capacity as an alumnus/alumna of another entity (such as an institution or program).
-
B.
alumnusRepresents
Indicates that an alumnus acts on behalf of, or serves as a representative of, a particular organization, group, or 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.
namedAlumnus
Indicates that an entity is explicitly identified or designated as an alumnus of another entity (such as an 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_69e245b911188190bc3d96326c847969 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1850df7fc81909ee522d99d96af0d |
completed | April 29, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69ef3ba004a48190885aece88efd1f52 |
completed | April 27, 2026, 10:34 a.m. |
| PDg | Predicate description generation | batch_69ef538b29c081908fa56ee35a1dcee7 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:53 p.m.