Triple
T12034521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltimore Beltway |
E286499
|
entity |
| Predicate | completedAsLoop |
P83959
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [Baltimore Beltway, completedAsLoop, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: completedAsLoop Context triple: [Baltimore Beltway, completedAsLoop, 1960s]
-
A.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
B.
completedBefore
Indicates that one event or action was fully completed prior to the start or completion of another specified event or action.
-
C.
completedAlongside
Indicates that one action, task, or process was completed at the same time and in coordination with another.
-
D.
completedAsThroughRoute
Indicates that an action or journey was carried out by following a designated through route from start to finish.
-
E.
loopCompletableIn
chosen
Indicates that a process, sequence, or cycle can be fully completed and brought back to its starting point under the given conditions.
- 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902b6ebbc8190b13c44a61c6f81b9 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:47 p.m.