Triple
T28080572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green |
E709663
|
entity |
| Predicate | isUsedToRepresent |
P41972
|
FINISHED |
| Object | specific transit routes |
—
|
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: specific transit routes | Statement: [Green, isUsedToRepresent, specific transit routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedToRepresent Context triple: [Green, isUsedToRepresent, specific transit routes]
-
A.
isRepresentiveOf
Indicates that one entity serves as an official agent, spokesperson, or proxy acting on behalf of another entity.
-
B.
isUsedToIllustrate
chosen
Indicates that one entity serves as an example or demonstration to clarify, explain, or represent another entity.
-
C.
isPartOfRepresentationSystem
Indicates that one entity functions as a component or element within a broader representational system (such as a notation, coding scheme, or symbolic framework).
-
D.
areRepresentedBy
Indicates that one entity serves as a representation, proxy, or stand-in for another entity.
-
E.
canRepresent
Indicates that one entity is capable of serving as a valid stand-in, proxy, or expression for another entity in a given context.
- 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_69ef9b7037f0819095bb90eaccbcaf32 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 8:51 p.m.