Triple
T33041943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transport typeface |
E845489
|
entity |
| Predicate | readingCondition |
P175732
|
FINISHED |
| Object | high-speed vehicle approach |
—
|
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: high-speed vehicle approach | Statement: [Transport typeface, readingCondition, high-speed vehicle approach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: readingCondition Context triple: [Transport typeface, readingCondition, high-speed vehicle approach]
-
A.
readingRequires
Indicates that performing a reading activity depends on or necessitates the presence or completion of another specified resource, condition, or prerequisite.
-
B.
readingOf
Indicates that one entity is an interpretation, measurement, or recorded value derived from another entity.
-
C.
containsReading
Indicates that one entity includes or encompasses a particular reading (such as a measurement, value, or interpretation) within it.
-
D.
readingType
Indicates the specific kind or category of reading associated with a measurement, observation, or recorded value.
-
E.
readingFeature
Indicates that an entity possesses a characteristic, capability, or attribute specifically related to reading.
- 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_69f34951348c8190b56746b0a7018182 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: May 1, 2026, 1:24 a.m.