Triple
T37511214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Call Mech |
E932520
|
entity |
| Predicate | replacesAbilityState |
P101291
|
FINISHED |
| Object | pilot mode |
—
|
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: pilot mode | Statement: [Call Mech, replacesAbilityState, pilot mode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacesAbilityState Context triple: [Call Mech, replacesAbilityState, pilot mode]
-
A.
replacementStatus
Indicates the state or condition of something in relation to being replaced, such as whether it has been, is being, or will be substituted by another.
-
B.
replacedCapabilityOf
chosen
Indicates that one capability has taken the place of, or superseded, another capability.
-
C.
hasAbilityState
Indicates that an entity possesses, lacks, or is in a particular condition regarding a specific ability or capability.
-
D.
replacedStatus
Indicates that one entity has taken the place of another, marking the original as superseded or no longer current.
-
E.
replacedWhenDisabledBy
Indicates that when one entity becomes disabled or nonfunctional, it is substituted or taken over by another entity.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe91383a1c81909266e40c3c3ede6c |
completed | May 9, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69fe8fde094081908f0f121664fbb5c7 |
completed | May 9, 2026, 1:37 a.m. |
Created at: May 3, 2026, 4:17 p.m.