Triple
T12899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 1394 |
E259
|
entity |
| Predicate | physicalLayer |
P1377
|
FINISHED |
| Object | IEEE 1394 physical layer specification |
—
|
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: IEEE 1394 physical layer specification | Statement: [IEEE 1394, physicalLayer, IEEE 1394 physical layer specification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: physicalLayer Context triple: [IEEE 1394, physicalLayer, IEEE 1394 physical layer specification]
-
A.
isMechanicalOrElectronic
Indicates that something operates using mechanical components, electronic components, or a combination of both.
-
B.
primaryStation
Indicates that one station is designated as the main or principal station associated with another entity or within a given context.
-
C.
isAnalogOrDigital
Indicates whether something operates using analog signals/representation or digital signals/representation.
-
D.
propulsion
Indicates a relationship where one entity provides the driving force or thrust that moves another entity forward or keeps it in motion.
-
E.
length
Indicates a measurement relationship where a value specifies how long something is from one end to the other.
- 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_69a23d7ad88c8190bffe8ab091d86642 |
completed | Feb. 28, 2026, 12:57 a.m. |
| NER | Named-entity recognition | batch_69a243abb2ec8190937365e5ecec52ad |
completed | Feb. 28, 2026, 1:23 a.m. |
| PD | Predicate disambiguation | batch_69a23fe9470c8190918a6ca1df168646 |
completed | Feb. 28, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69a243aa85848190813154e8a6495200 |
completed | Feb. 28, 2026, 1:23 a.m. |
Created at: Feb. 28, 2026, 1:02 a.m.