Triple
T32880842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TPG bus lines |
E841060
|
entity |
| Predicate | hasComplementaryMode |
P205184
|
FINISHED |
| Object | TPG tram lines |
—
|
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: TPG tram lines | Statement: [TPG bus lines, hasComplementaryMode, TPG tram lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComplementaryMode Context triple: [TPG bus lines, hasComplementaryMode, TPG tram lines]
-
A.
hasComplementaryColor
Indicates that one color is the complementary (i.e., opposite on the color wheel, providing maximum contrast) counterpart of another color.
-
B.
hasCompatibilityMode
Indicates that one entity operates under a special mode or setting designed to maintain compatibility with another entity or with an earlier version.
-
C.
hasComplementaryOperator
Indicates that one operator is associated with another operator that performs a complementary or inverse function to it.
-
D.
hasPrimaryModeSupported
Indicates that an entity supports a particular mode as its main or default mode of operation.
-
E.
supportsCompanion
Indicates that one entity provides assistance, encouragement, or backing to another entity in a companion or partner role.
- 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_69f349446e288190a70c05bcc4d81172 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037cab06288190b093935f235ddff2 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:18 a.m.