Triple
T29005316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iroquois warriors |
E736413
|
entity |
| Predicate | followedCustom |
P186370
|
FINISHED |
| Object | mourning wars |
—
|
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: mourning wars | Statement: [Iroquois warriors, followedCustom, mourning wars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followedCustom Context triple: [Iroquois warriors, followedCustom, mourning wars]
-
A.
followedIn
Indicates that one entity began following or subscribing to another entity, typically in a social or sequential context.
-
B.
followedCampaign
Indicates that an entity chose to subscribe to or track updates from a particular campaign.
-
C.
followedPerson
Indicates that one person has chosen to follow another person, typically to receive updates or track their activities.
-
D.
followedSign
Indicates that an entity proceeded in accordance with, or took action based on, a particular sign or posted instruction.
-
E.
adoptedFollowing
Indicates that one entity formally took on or implemented another entity after or as a result of the occurrence of a preceding event, state, or action.
- 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7cec398ac819081c954a993c323ee |
completed | May 3, 2026, 10:40 p.m. |
Created at: April 28, 2026, 9:37 a.m.