Triple
T34403620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rose Creek |
E883048
|
entity |
| Predicate | defendedByCharacter |
P54263
|
FINISHED |
| Object | Sam Chisolm |
—
|
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: Sam Chisolm | Statement: [Rose Creek, defendedByCharacter, Sam Chisolm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defendedByCharacter Context triple: [Rose Creek, defendedByCharacter, Sam Chisolm]
-
A.
defendsCharacter
Indicates that one entity protects, supports, or argues in favor of another entity, especially in the face of criticism, attack, or threat.
-
B.
titleDefendedBy
Indicates that a specific title or championship is actively defended or held against challengers by a particular entity.
-
C.
defendedAs
Indicates that one entity is presented, argued, or justified as being equivalent to or serving the role of another entity in a defensive or protective context.
-
D.
defenderIn
chosen
Indicates that an entity serves as a defensive agent or protector within a specified context, situation, or domain.
-
E.
isDefendedOn
Indicates that one entity provides protection, justification, or support for another entity in a specific context or situation.
- 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_69f349c1f2208190a09a489bb8b2719d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: May 1, 2026, 1:59 a.m.