Triple
T27981550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shirley Crabtree Jr. |
E706636
|
entity |
| Predicate | hadFeudWith |
P109978
|
FINISHED |
| Object | Giant Haystacks |
—
|
NE NERFINISHED |
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: Giant Haystacks | Statement: [Shirley Crabtree Jr., hadFeudWith, Giant Haystacks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadFeudWith Context triple: [Shirley Crabtree Jr., hadFeudWith, Giant Haystacks]
-
A.
hadFeudatory
Indicates that one entity served as a subordinate or vassal state under the authority or suzerainty of another entity.
-
B.
feudedWith
chosen
Indicates a prolonged, often hostile conflict or rivalry between two entities.
-
C.
inspiredFeudWith
Indicates that one entity’s actions, ideas, or influence sparked or provoked a feud or ongoing conflict with another entity.
-
D.
fought
Indicates that one entity engaged in physical or armed conflict or combat against another entity.
-
E.
hasCauseOfConflict
Indicates a relationship where one entity is the source or reason for a conflict involving another entity.
- 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_69ef96b8b8d88190bad5e4ae966bf14e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63b693f448190b334a8a505aee5ad |
completed | May 2, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:44 p.m.