Triple
T26271316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Farragut Crossing (virtual tunnel) |
E660429
|
entity |
| Predicate | transferMechanism |
P39909
|
FINISHED |
| Object | fare system linkage |
—
|
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: fare system linkage | Statement: [Farragut Crossing (virtual tunnel), transferMechanism, fare system linkage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferMechanism Context triple: [Farragut Crossing (virtual tunnel), transferMechanism, fare system linkage]
-
A.
transferMode
chosen
Indicates the method or mechanism by which something is transferred from one entity to another.
-
B.
transferType
Indicates the specific method or category of how something is transferred from one entity to another.
-
C.
transferBetween
Indicates a movement or handover of something from one entity to another, typically changing its location, ownership, or control between them.
-
D.
transitionMechanismUsedWith
Indicates that a particular transition or change from one state to another is carried out using a specified mechanism or method.
-
E.
transferFeature
Indicates a relationship where a feature, attribute, or capability is moved or reassigned from one entity 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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 26, 2026, 9:50 p.m.