Triple
T4077335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INSEAD |
E87394
|
entity |
| Predicate | hasAlumniPresenceIn |
P14540
|
FINISHED |
| Object | more than 170 countries |
—
|
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: more than 170 countries | Statement: [INSEAD, hasAlumniPresenceIn, more than 170 countries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlumniPresenceIn Context triple: [INSEAD, hasAlumniPresenceIn, more than 170 countries]
-
A.
hasAlumni
Indicates that an institution or organization is associated with individuals who formerly attended or graduated from it.
-
B.
hasAlumniInvolvement
Indicates that an entity maintains an ongoing relationship or engagement with its former members or graduates.
-
C.
hasAlumniNetwork
chosen
Indicates that an entity maintains or is associated with an organized network or community of its former members or graduates.
-
D.
hasAlumnusLeague
Indicates that an educational institution has at least one alumnus who is or was a member of a specified sports league.
-
E.
hadAlumniRole
Indicates that an entity previously held a role or position as an alumnus/alumna of another entity (such as an institution or organization).
- 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_69aed9435cf48190ad1da737c962d19d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc4d348c8190a94724639830aca0 |
completed | March 9, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69aef9082c2081908474f082a49bebc8 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.