Triple
T24822332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | maxwell |
E621093
|
entity |
| Predicate | unitSystemStatus |
P35303
|
FINISHED |
| Object | non-SI unit accepted only for historical use |
—
|
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: non-SI unit accepted only for historical use | Statement: [maxwell, unitSystemStatus, non-SI unit accepted only for historical use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unitSystemStatus Context triple: [maxwell, unitSystemStatus, non-SI unit accepted only for historical use]
-
A.
hasUnitStatus
chosen
Indicates that an entity is associated with a particular operational or condition status as a unit.
-
B.
operatorStatus
Indicates the current operational state or condition of an operator (e.g., active, inactive, or in error).
-
C.
exportStatus
Indicates the current state or outcome of an entity’s export process (e.g., pending, in progress, completed, or failed).
-
D.
NLManagerStatus
Indicates the current operational state or condition of a natural language manager within a system.
-
E.
statusInterface
Indicates that an entity serves as, or is associated with, an interface that reports or reflects its current status.
- 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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:04 a.m.