Triple
T17885638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fade |
E447192
|
entity |
| Predicate | canPhaseOthers |
P129145
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Fade, canPhaseOthers, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canPhaseOthers Context triple: [Fade, canPhaseOthers, true]
-
A.
targetsPhase
Indicates that an action, process, or entity is specifically directed toward or intended to affect a particular phase or stage within a larger sequence or lifecycle.
-
B.
canElect
Indicates that one entity has the authority or ability to choose another entity for a position, role, or office through an election process.
-
C.
phasesOut
Indicates the process by which one entity or condition is gradually discontinued or removed in favor of another over time.
-
D.
applicationPhase
Indicates the specific stage or step an application is currently in within a broader application process.
-
E.
hasCompetingPhase
Indicates that one phase exists in a competitive or mutually exclusive relationship with another phase, such that they cannot or do not occur fully at the same time.
- F. None of above. chosen
Provenance (4 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49c123748819091bf46178105079b |
completed | April 19, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e9b77c8190bbfb508f28dfacfa |
completed | April 18, 2026, 7:18 p.m. |
| PDg | Predicate description generation | batch_69e3db7704588190a34a422421152173 |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:18 a.m.