Triple
T33999219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aerobús express airport bus |
E871768
|
entity |
| Predicate | typicalRouteEndpoint |
P148404
|
FINISHED |
| Object | Plaça de Catalunya |
E276262
|
NE 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: Plaça de Catalunya | Statement: [Aerobús express airport bus, typicalRouteEndpoint, Plaça de Catalunya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRouteEndpoint Context triple: [Aerobús express airport bus, typicalRouteEndpoint, Plaça de Catalunya]
-
A.
typicalEndpoint
chosen
Indicates that something represents the standard or commonly used endpoint associated with another entity or process.
-
B.
typicalEntryRoute
Indicates the usual or most common path or method by which something is entered or accessed.
-
C.
exampleRoute
Indicates a route that serves as a representative or illustrative path among possible routes between locations.
-
D.
endPoint
Indicates the terminal location, limit, or final state reached by an object, process, or path in a given relationship or action.
-
E.
testingRoute
Indicates that an entity follows or is assigned to a route used specifically for testing or validation purposes rather than regular operation.
- F. None of above.
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_69f3499f8cbc81908de6ec89fa91ea8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3748cf9b2c8190b09b0208c0f8bf39 |
completed | June 21, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:50 a.m.