Triple
T30040342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twin Bridges |
E763281
|
entity |
| Predicate | hasParallelStructures |
P48977
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Twin Bridges, hasParallelStructures, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParallelStructures Context triple: [Twin Bridges, hasParallelStructures, 2]
-
A.
structureParallels
Indicates that the structural organization or arrangement of one entity closely corresponds to or mirrors that of another.
-
B.
hasParallelIn
Indicates that one entity has a corresponding or analogous counterpart in another context, system, or domain.
-
C.
hasConceptualParallel
Indicates that one entity corresponds to or mirrors another at a conceptual level, showing a similar idea, structure, or pattern despite possible differences in form or context.
-
D.
hasParallelTransit
Indicates that one transit route, service, or segment runs in parallel to another along a similar path or corridor.
-
E.
hasTwoPartStructure
chosen
Indicates that something is composed of exactly two distinct, structured parts that together form a whole.
- 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_69f2246fb2b88190acff36bf7975c8f0 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
Created at: April 29, 2026, 6:52 p.m.