Triple
T35626456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAM 26000 |
E1029468
|
entity |
| Predicate | currentDisplayStatus |
P45152
|
FINISHED |
| Object | on static display |
—
|
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: on static display | Statement: [SAM 26000, currentDisplayStatus, on static display]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentDisplayStatus Context triple: [SAM 26000, currentDisplayStatus, on static display]
-
A.
displayState
chosen
Indicates the current visual or presentation status of an item, such as whether and how it is shown, hidden, or rendered in a user interface or display context.
-
B.
currentDisplayLocation
Indicates the location or context where something is presently being shown or rendered.
-
C.
actualStatus
Indicates the current, real-world state or condition of an entity, as opposed to a planned, expected, or nominal status.
-
D.
consoleStatus
Indicates the current operational or state condition of a console within a system or environment.
-
E.
statusOnShow
Indicates the status or condition an entity has specifically when it is being shown or displayed.
- 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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff6fba1a5c8190a660279a6271d785 |
completed | May 9, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69ff6f59388c8190a7d6ab7bc7705bc0 |
completed | May 9, 2026, 5:31 p.m. |
Created at: May 3, 2026, 4:05 p.m.