Triple
T37504448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GENEVA (informal Metra designation) |
E932055
|
entity |
| Predicate | codeSystemStatus |
P121986
|
FINISHED |
| Object | informal |
—
|
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: informal | Statement: [GENEVA (informal Metra designation), codeSystemStatus, informal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeSystemStatus Context triple: [GENEVA (informal Metra designation), codeSystemStatus, informal]
-
A.
standardCodeSystem
Indicates that an entity uses or is associated with a recognized, authoritative coding or classification system as its reference standard.
-
B.
classStatus
Indicates the current academic or enrollment standing of an entity within a class or course context.
-
C.
exportStatus
Indicates the current state or outcome of an entity’s export process (e.g., pending, in progress, completed, or failed).
-
D.
statusInSystem7
chosen
Indicates that an entity holds a particular status or state within the context of system 7.
-
E.
regionCodeSystem
Indicates that a region is identified or classified according to a particular coding system for geographic or administrative areas.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.