Triple
T34127364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torres House |
E875322
|
entity |
| Predicate | isOriginalStructureOf |
P52639
|
FINISHED |
| Object | Torres House addition |
—
|
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: Torres House addition | Statement: [Torres House, isOriginalStructureOf, Torres House addition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOriginalStructureOf Context triple: [Torres House, isOriginalStructureOf, Torres House addition]
-
A.
originalStructureType
Indicates the type or category of the structure that an entity originally had before any changes or transformations.
-
B.
originalStructureStatus
Indicates the condition or state of an entity’s initial or pre-modified structure relative to its later or current form.
-
C.
hasOriginalComposition
Indicates that one entity is the initial or primary compositional source or makeup of another entity.
-
D.
relationshipToOriginalStructure
Indicates the nature or degree of connection that something has to its initial or source structure.
-
E.
containsStructureFrom
chosen
Indicates that one entity includes or incorporates a structural component originating from another entity.
- 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_69f349aa33848190a2e6c5e4533c8444 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:53 a.m.