Triple
T11094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington Metro |
E225
|
entity |
| Predicate | planningStart |
P288
|
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: [Washington Metro, planningStart, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planningStart Context triple: [Washington Metro, planningStart, 1960s]
-
A.
startDate
chosen
Indicates the point in time when an event, state, or relationship begins.
-
B.
startPoint
Indicates the initial location or position from which an object, path, or action begins.
-
C.
plannedFacility
Indicates that a facility is intended or scheduled to be built, established, or implemented in the future but does not yet exist or operate.
-
D.
coordinatedWith
Indicates that two or more entities have worked together in an organized, cooperative manner toward a shared task, goal, or activity.
-
E.
proposes
Indicates that one entity formally suggests or puts forward an idea, plan, or course of action to another entity for consideration or approval.
- 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_69a23d7ad88c8190bffe8ab091d86642 |
completed | Feb. 28, 2026, 12:57 a.m. |
| NER | Named-entity recognition | batch_69a242cd8fb481909562f114f4ce7700 |
completed | Feb. 28, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69a23fe6b0bc8190bcce9b74f2c5fb08 |
completed | Feb. 28, 2026, 1:07 a.m. |
Created at: Feb. 28, 2026, 1:02 a.m.