Triple
T27981614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giant Haystacks |
E706638
|
entity |
| Predicate | usedRingNameInPromotion |
P164550
|
FINISHED |
| Object | Loch Ness in WCW |
—
|
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: Loch Ness in WCW | Statement: [Giant Haystacks, usedRingNameInPromotion, Loch Ness in WCW]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedRingNameInPromotion Context triple: [Giant Haystacks, usedRingNameInPromotion, Loch Ness in WCW]
-
A.
usedRingNameUntil
Indicates that an entity used a particular ring name as their professional or public identity up until a specified time or event.
-
B.
usesPromotion
Indicates that an entity applies or takes advantage of a specific promotion, discount, or special offer.
-
C.
usesPromotionFrom
Indicates that one entity applies or benefits from a promotion, discount, or marketing offer provided or originated by another entity.
-
D.
originalRingName
Indicates the name originally used for a ring before any later changes or renamings.
-
E.
usesRingStyle
Indicates that one entity performs or operates using a particular ring-based style, method, or format.
- 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_69ef96b8b8d88190bad5e4ae966bf14e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f64e6e8c9081908ce4d364aa26147a |
completed | May 2, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 27, 2026, 7:44 p.m.