Triple
T37813025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weasel Stop |
E942698
|
entity |
| Predicate | featuresBattleOfWitsBetween |
P47597
|
FINISHED |
| Object | Foghorn Leghorn and a hungry weasel |
—
|
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: Foghorn Leghorn and a hungry weasel | Statement: [Weasel Stop, featuresBattleOfWitsBetween, Foghorn Leghorn and a hungry weasel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresBattleOfWitsBetween Context triple: [Weasel Stop, featuresBattleOfWitsBetween, Foghorn Leghorn and a hungry weasel]
-
A.
featuresBattle
chosen
Indicates that one entity includes, presents, or involves a battle as a significant element or event.
-
B.
epicBattle
Indicates a large-scale, intense conflict or confrontation between opposing entities, often marked by extraordinary stakes or dramatic significance.
-
C.
battleOpponent
Indicates that two entities are engaged in or designated as opponents in a battle or combat scenario.
-
D.
coveredBattle
Indicates that an entity reported on, documented, or otherwise provided coverage of a particular battle or military engagement.
-
E.
combatBy
Indicates a relationship where one entity engages in combat or fighting through the agency, actions, or involvement of 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_69f76ee8104c8190ab17133ccd8f86e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:19 p.m.