Triple
T38232839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia University Morningside Heights campus |
E1013535
|
entity |
| Predicate | hasNotableBuildingArchitect |
P42691
|
FINISHED |
| Object | Charles Follen McKim |
E26183
|
NE 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: Charles Follen McKim | Statement: [Columbia University Morningside Heights campus, hasNotableBuildingArchitect, Charles Follen McKim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableBuildingArchitect Context triple: [Columbia University Morningside Heights campus, hasNotableBuildingArchitect, Charles Follen McKim]
-
A.
architectIsNotableFor
Indicates that an architect is recognized or distinguished for a particular work, contribution, or achievement.
-
B.
architectNotedFor
Indicates that an architect is recognized or distinguished for a particular work, style, contribution, or achievement.
-
C.
hasLandmarkArchitect
chosen
Indicates that a landmark is associated with, or was designed by, a specific architect.
-
D.
hasArchitectNotability
Indicates that an entity is notable or recognized specifically for its work or role as an architect.
-
E.
hasCountryArchitect
Indicates that an entity has an architect associated with a specific country.
- F. None of above.
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_69f76dd72a248190a5fe18db2bd1eb15 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a419df0a3a48190af2641e10a9b8aaa |
completed | June 28, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.