Triple
T6509789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strætó bus system |
E150096
|
entity |
| Predicate | identification |
P3732
|
FINISHED |
| Object | yellow buses with Strætó branding |
—
|
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: yellow buses with Strætó branding | Statement: [Strætó bus system, identification, yellow buses with Strætó branding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identification Context triple: [Strætó bus system, identification, yellow buses with Strætó branding]
-
A.
identifierFor
chosen
Indicates that one entity serves as a unique identifying label or code for another entity.
-
B.
identityRevealedIn
Indicates that an entity’s true identity becomes known or disclosed within a specified context, source, or situation.
-
C.
identityConcept
Indicates that two concepts are the same in identity, representing exactly the same underlying idea or meaning.
-
D.
selfIdentification
Indicates that an entity defines or declares its own identity, attributes, or classification about itself.
-
E.
identityIssue
Indicates that an entity is experiencing uncertainty, conflict, or problems related to its sense of identity or self-definition.
- 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_69c687ef291081909d437f035eef1cda |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c69f398f10819096342f3646cefcc2 |
completed | March 27, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69c68ab98c78819081743e614df04e1d |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:43 p.m.