Triple
T28930035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 1496-1993 |
E733754
|
entity |
| Predicate | hasBusType |
P175660
|
FINISHED |
| Object | synchronous bus |
—
|
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: synchronous bus | Statement: [IEEE 1496-1993, hasBusType, synchronous bus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBusType Context triple: [IEEE 1496-1993, hasBusType, synchronous bus]
-
A.
hasCabType
Indicates that an entity is associated with or characterized by a specific type or category of cab.
-
B.
isTransportationType
Indicates that one entity functions as a mode or category of transportation for the other entity.
-
C.
hasBusOperator
Indicates that a bus service, route, or vehicle is operated or managed by a specific operator or company.
-
D.
hasBusServices
Indicates that one location or entity is served by bus routes or bus transportation provided by another.
-
E.
hasBusTerminalType
Indicates the specific category or type of bus terminal associated with an entity.
- 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_69f05b0b49b08190b8994b339c7980f6 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: April 28, 2026, 8:27 a.m.