Triple
T26407155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macaulay Honors College |
E663864
|
entity |
| Predicate | hasProgramAt |
P126496
|
FINISHED |
| Object | Hunter College |
—
|
NE NERFINISHED |
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: Hunter College | Statement: [Macaulay Honors College, hasProgramAt, Hunter College]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProgramAt Context triple: [Macaulay Honors College, hasProgramAt, Hunter College]
-
A.
hasProgramCode
Indicates that an entity is associated with a specific program identifier or code used to reference or classify it within a system.
-
B.
hasProgramElement
Indicates that one entity contains, includes, or is associated with a specific program element (such as a function, class, module, or code component).
-
C.
hasProgramLocation
chosen
Indicates that a program, event, or activity takes place at or is associated with a specific location.
-
D.
hasCalledProgram
Indicates that one program has invoked or executed another program.
-
E.
hasProgramCounter
Indicates that an entity is associated with a program counter, i.e., a register or mechanism that tracks the address of the next instruction to be executed.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: April 26, 2026, 11:35 p.m.