Triple
T32160388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rooms |
E821405
|
entity |
| Predicate | hasCompanionSections |
—
|
GENERATED |
| Object | Objects |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
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 (1 batch)
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. |
Created at: May 1, 2026, 12:32 a.m.