Triple
T37423120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roncesvalles streetcar routes |
E929914
|
entity |
| Predicate | provideConnectionType |
P1374
|
FINISHED |
| Object | north–south transit connection |
—
|
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: north–south transit connection | Statement: [Roncesvalles streetcar routes, provideConnectionType, north–south transit connection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: provideConnectionType Context triple: [Roncesvalles streetcar routes, provideConnectionType, north–south transit connection]
-
A.
connectorType
chosen
Indicates the specific kind or category of connection interface that links two entities.
-
B.
namingConnectionType
Indicates a relationship specifying the type or nature of a naming connection that exists between two entities.
-
C.
honorsConnectionType
Indicates that one entity formally recognizes, respects, or commemorates another entity or their relationship in a special or distinguished way.
-
D.
connectsServiceType
Indicates a relationship where one entity is linked or associated to another based on a specific type of service connection.
-
E.
connectorTypeDesignation
Indicates the specific type or classification assigned to a connector within a connection or interface relationship.
- 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_69f76ebf0f288190ba198a78341613b8 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69feced53a7c819098ec474fb7d514b0 |
completed | May 9, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69fecd9cd5288190aac8b4e04a7ee78e |
completed | May 9, 2026, 6:01 a.m. |
Created at: May 3, 2026, 4:16 p.m.