Triple
T16747115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSAP |
E406984
|
entity |
| Predicate | commandResponseBitPosition |
P91207
|
FINISHED |
| Object | least significant bit |
—
|
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: least significant bit | Statement: [SSAP, commandResponseBitPosition, least significant bit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandResponseBitPosition Context triple: [SSAP, commandResponseBitPosition, least significant bit]
-
A.
currentPosition
Indicates the present role, job, or status an entity currently holds within a given context.
-
B.
positionInMessage
chosen
Indicates the specific location or index where something appears within a message.
-
C.
positionOnRecord
Indicates the specific place or rank an item occupies within an ordered record or listing.
-
D.
futurePosition
Indicates that one entity will occupy or hold the position, role, or location of another entity at a later point in time.
-
E.
continuityPosition
Indicates the relative ordering or placement of an element within a continuous sequence or flow of related elements.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa2311748190a17416de577ad159 |
completed | April 18, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.