Triple
T19488639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yale School of the Environment |
E487584
|
entity |
| Predicate | KroonHallFunction |
P114096
|
FINISHED |
| Object | main academic building |
—
|
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: main academic building | Statement: [Yale School of the Environment, KroonHallFunction, main academic building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: KroonHallFunction Context triple: [Yale School of the Environment, KroonHallFunction, main academic building]
-
A.
hasHallFunction
chosen
Indicates that an entity serves as or includes a hall used for gatherings, events, or similar functions.
-
B.
corridorFunction
Indicates that one entity serves as a corridor or passageway functionally connecting or providing access between other spaces or areas.
-
C.
cucullusFunction
Indicates that one entity serves as the functional hood- or cowl-like covering (cucullus) for another entity.
-
D.
castleFunction
Indicates the primary role, purpose, or use that a castle serves (e.g., defense, residence, administration, or symbolism).
-
E.
hasSingleHall
Indicates that an entity possesses exactly one hall within its structure or domain.
- 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_69d8e8d924388190b847cb15bb3d0aff |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e634432af08190984e988935fd14bd |
completed | April 20, 2026, 2:12 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7883308190b73912a71a35a835 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.