Triple
T12160736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Building |
E289697
|
entity |
| Predicate | complexType |
P25843
|
FINISHED |
| Object | mixed-use development |
—
|
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: mixed-use development | Statement: [North Building, complexType, mixed-use development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: complexType Context triple: [North Building, complexType, mixed-use development]
-
A.
partOfComplexType
Indicates that an entity functions as a component or member within a larger, composite structure or complex type.
-
B.
complexName
Indicates that an entity has a multi-part or structurally intricate name, typically composed of several elements or components.
-
C.
cornerComplexType
Indicates a relationship where something is positioned, formed, or structured at or around a corner in a complex or composite manner.
-
D.
hasComplex
Indicates that one entity possesses, is associated with, or is part of a larger composite structure or complex formed with another entity.
-
E.
compositionForm
chosen
Indicates the structural or organizational form in which something is composed or arranged.
- 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915d7109481908bf5fe512bba3c89 |
completed | April 10, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69d9150c18148190bf8152189c0e5fca |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:50 p.m.