Triple
T29920519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McIntosh |
E759914
|
entity |
| Predicate | hasExperienceWith |
P141157
|
FINISHED |
| Object | Apache warfare |
—
|
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: Apache warfare | Statement: [McIntosh, hasExperienceWith, Apache warfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExperienceWith Context triple: [McIntosh, hasExperienceWith, Apache warfare]
-
A.
hasExperienceOf
chosen
Indicates that one entity has undergone, encountered, or lived through a particular event, situation, or activity associated with another entity.
-
B.
hasPastExperience
Indicates that an entity has previously engaged in or undergone the specified activity, role, or situation in the past.
-
C.
hasExperienceElement
Indicates that an experience is composed of, or includes, a specific constituent element or component.
-
D.
usedExperienceIn
Indicates that an entity applied or leveraged a particular experience or expertise in performing an action or achieving a result.
-
E.
hasNotableExperience
Indicates that an entity has a significant or distinguished experience related to another entity or context.
- 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_69f2246189fc8190996b63ee1f9a2374 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 29, 2026, 6:14 p.m.