Triple
T17183563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lime House |
E417040
|
entity |
| Predicate | hasRelationshipToOtherUnits |
P73892
|
FINISHED |
| Object | One of multiple sections in Pod complex |
—
|
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: One of multiple sections in Pod complex | Statement: [Lime House, hasRelationshipToOtherUnits, One of multiple sections in Pod complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelationshipToOtherUnits Context triple: [Lime House, hasRelationshipToOtherUnits, One of multiple sections in Pod complex]
-
A.
isRelatedUnit
chosen
Indicates that one unit has a defined relationship or association with another unit within a given system or context.
-
B.
hasNeighborRelationshipWith
Indicates that one entity is located adjacent to or directly next to another entity, sharing a neighbor relationship.
-
C.
associatedUnitType
Indicates that one entity is linked to or characterized by a particular type or category of unit.
-
D.
hasParentUnit
Indicates that one unit is hierarchically contained within or belongs to another, higher-level unit.
-
E.
relationshipToUNITAF
Indicates the specific type or nature of an entity’s relationship or affiliation with UNITAF.
- 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42d9416a48190a5930fcd6008dbaa |
completed | April 19, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.