Triple
T33943838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2013 Catalan Way human chain |
E870236
|
entity |
| Predicate | usedTransportForAccess |
P147666
|
FINISHED |
| Object | buses |
—
|
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: buses | Statement: [2013 Catalan Way human chain, usedTransportForAccess, buses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedTransportForAccess Context triple: [2013 Catalan Way human chain, usedTransportForAccess, buses]
-
A.
usesTransport
Indicates that an entity employs or relies on a particular mode or means of transportation to move from one place to another.
-
B.
transportAccessType
chosen
Indicates the type or mode of transportation access available or used in a given context.
-
C.
usesTransportNetwork
Indicates that an entity makes use of a transport network (such as roads, rail, or transit systems) to move people, goods, or services.
-
D.
allowedTransport
Indicates that a particular mode or means of transport is permitted for use between the related entities.
-
E.
isTransport
Indicates that one entity serves as a means or method for conveying or carrying another entity from one place to another.
- 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_69f3499b0dd48190b07b4b60babcee02 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: May 1, 2026, 1:49 a.m.