Triple
T16042007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Willis Faber and Dumas |
E389119
|
entity |
| Predicate | notableBuildingUse |
P5773
|
FINISHED |
| Object | corporate headquarters |
—
|
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: corporate headquarters | Statement: [Willis Faber and Dumas, notableBuildingUse, corporate headquarters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBuildingUse Context triple: [Willis Faber and Dumas, notableBuildingUse, corporate headquarters]
-
A.
buildingUsedBy
Indicates that a particular building is utilized or occupied by a specified entity for some purpose.
-
B.
notableUse
chosen
Indicates that something is prominently or famously used by a particular entity, context, or for a specific purpose.
-
C.
notableBuildingAssociated
Indicates a relationship where a notable or significant building is associated with, connected to, or relevant to a given entity.
-
D.
notableConstructionCenter
Indicates that a place serves as a significant hub or focal point for construction activity or construction-related operations.
-
E.
architecturalUse
Indicates how a structure, space, or element is intended to be used or function within an architectural context.
- 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1826f34c081908005bb736f1c485d |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:56 a.m.