Triple
T9008296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crenshaw/LAX Transit Project |
E215399
|
entity |
| Predicate | projectLength |
P85699
|
FINISHED |
| Object | approximately 8.5 miles |
—
|
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: approximately 8.5 miles | Statement: [Crenshaw/LAX Transit Project, projectLength, approximately 8.5 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectLength Context triple: [Crenshaw/LAX Transit Project, projectLength, approximately 8.5 miles]
-
A.
workLength
Indicates the duration or length of time associated with a particular work or task.
-
B.
projectNumber
Indicates a relationship where a specific identifying number is assigned to or associated with a particular project.
-
C.
projectModel
Indicates a relationship where one entity serves as a model, template, or representation for a project or projected outcome involving another entity.
-
D.
programLength
Indicates the duration or total length of a program, typically measured in time or size.
-
E.
project
Indicates that an entity plans, organizes, or carries out a structured effort or initiative aimed at achieving a specific goal or outcome.
- F. None of above. chosen
Provenance (4 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_69ca83a2bf088190986ee7a8eb90407d |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc69bed8588190afc9cbca12b75a3b |
completed | April 1, 2026, 12:41 a.m. |
| PD | Predicate disambiguation | batch_69cc5edf84408190aa5f57cb8bfd00e1 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f6dec4081909379bd57c02a5710 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:06 p.m.