Triple
T36194606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R188 |
E1047086
|
entity |
| Predicate | fleetNumberRangeIncludes |
P44071
|
FINISHED |
| Object | 7811 |
—
|
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: 7811 | Statement: [R188, fleetNumberRangeIncludes, 7811]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fleetNumberRangeIncludes Context triple: [R188, fleetNumberRangeIncludes, 7811]
-
A.
planeNumberRangeStart
Indicates the starting value of a numerical range assigned to plane numbers within a specified interval.
-
B.
fleetNumbers
chosen
Indicates that there is an association between an entity and one or more identifying numbers assigned to it as part of a fleet.
-
C.
planeNumberRangeEnd
Indicates the upper bound value in a specified range of plane numbers within which something applies or is valid.
-
D.
operatorFleetNumberRangeAmtrak
Indicates that the operator’s fleet numbers for the referenced Amtrak vehicles fall within a specified numeric range.
-
E.
hullNumberRange
Indicates a relationship where an entity’s hull number falls within a specified numeric range.
- 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_69f76e3d4fbc81908c159c7beeb4ce00 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.