Triple
T18082123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bat MacPherson |
E432717
|
entity |
| Predicate | hasPastActions |
P39943
|
FINISHED |
| Object | cause conflict with other pilots |
—
|
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: cause conflict with other pilots | Statement: [Bat MacPherson, hasPastActions, cause conflict with other pilots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPastActions Context triple: [Bat MacPherson, hasPastActions, cause conflict with other pilots]
-
A.
hasHistoryIn
Indicates that an entity has a past involvement, presence, or record of activity within a particular domain, context, or location.
-
B.
hasTimeOfAction
Indicates that an action is associated with a specific point or interval in time when it occurs.
-
C.
hasAct
Indicates that an entity performs, participates in, or is associated with a specific act or action.
-
D.
hasHad
chosen
Indicates that an entity previously experienced, possessed, or was involved in something at some point in the past.
-
E.
hasHistoricMine
Indicates that an entity possesses, contains, or is the site of a mine that is of historical significance.
- 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_69d8b907d05c819083cc3bd6021089e6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4d9fb42888190919fe711a281bd7c |
completed | April 19, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69e3f90c652481908133a73106d78919 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:27 a.m.