Triple
T32708786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XAResource |
E836342
|
entity |
| Predicate | usedForPhase |
P98
|
FINISHED |
| Object | transaction prepare phase |
—
|
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: transaction prepare phase | Statement: [XAResource, usedForPhase, transaction prepare phase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForPhase Context triple: [XAResource, usedForPhase, transaction prepare phase]
-
A.
phaseUsed
Indicates that a particular phase, stage, or step is utilized or applied in carrying out an action, process, or relationship.
-
B.
usedInConflictPhase
Indicates that an action, resource, or strategy is employed during a specific phase or stage of a conflict.
-
C.
usedFor
chosen
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
D.
typicalUsagePhase
Indicates the phase or stage in which something is most commonly or characteristically used.
-
E.
appliesToPhase
Indicates that a particular rule, condition, or action is relevant to and operates during a specific phase within a process or lifecycle.
- 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 1, 2026, 1:10 a.m.