Triple
T32160388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rooms |
E821405
|
entity |
| Predicate | hasCompanionSections |
P206201
|
FINISHED |
| Object | Objects |
—
|
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: Objects | Statement: [Rooms, hasCompanionSections, Objects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompanionSections Context triple: [Rooms, hasCompanionSections, Objects]
-
A.
hasCompanionContent
Indicates that one piece of content is accompanied by related or supplementary content intended to be used or consumed together.
-
B.
hasCompanionPillar
Indicates that an entity is associated with or supported by a corresponding companion pillar.
-
C.
includesCompanion
Indicates that one entity involves, contains, or is accompanied by another entity acting as a companion.
-
D.
hasCompanionRoute
Indicates that one route is associated with another route that serves as its companion, typically running in parallel, in the opposite direction, or as a complementary service.
-
E.
hasCompanionCase
Indicates that an entity is associated with another related case that accompanies or parallels it.
- F. None of above. chosen
Provenance (4 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_69f34905e098819082191a6922a6d607 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 12:32 a.m.