Triple
T22321304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Utah Trail |
E551791
|
entity |
| Predicate | hasLeadCharacterType |
P10724
|
FINISHED |
| Object | singing cowboy |
—
|
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: singing cowboy | Statement: [The Utah Trail, hasLeadCharacterType, singing cowboy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeadCharacterType Context triple: [The Utah Trail, hasLeadCharacterType, singing cowboy]
-
A.
hasTypicalCharacterType
chosen
Indicates that an entity is commonly associated with or exemplified by a particular type of character or persona.
-
B.
hasLeadCharacterGender
Indicates that the primary or lead character in a work has a specified gender.
-
C.
hasCharacterClass
Indicates that an entity (such as a character) belongs to or is assigned a particular character class or role type.
-
D.
hasMainTitleCharacter
Indicates that a work’s primary or main title is centered on, derived from, or explicitly names a particular character.
-
E.
leadCharacterStatus
Indicates the role or condition of an entity when it serves as the primary or central character in a narrative or context.
- 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_69e11e4776588190abb21e5cea79973f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15764d3a48190af79ce4642b7f563 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:42 p.m.