Triple
T13526507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | andon |
E323027
|
entity |
| Predicate | signals |
P58686
|
FINISHED |
| Object | normal operation |
—
|
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: normal operation | Statement: [andon, signals, normal operation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signals Context triple: [andon, signals, normal operation]
-
A.
digitalSignal
Indicates that the relationship or action involves representing, transmitting, or processing information as a discrete-time, discrete-value (digital) signal between entities.
-
B.
signalContent
chosen
Indicates that one entity is the informational content or message carried, conveyed, or represented by a signal produced or transmitted by another entity.
-
C.
signalType
Indicates the specific kind or category of signal associated with or used by an entity or interaction.
-
D.
controlSignals
Indicates that one entity sends or governs directive signals that determine or influence the behavior or operation of another entity.
-
E.
militarySignal
Indicates a relationship where one party sends or uses a signal for military or defense-related purposes toward another party or target.
- 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafa6ad60819087824e4ac83934ed |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:44 p.m.