Triple
T16673750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Half-Breed |
E405165
|
entity |
| Predicate | mainCharacterDescent |
P33454
|
FINISHED |
| Object | half Cherokee |
—
|
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: half Cherokee | Statement: [Half-Breed, mainCharacterDescent, half Cherokee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCharacterDescent Context triple: [Half-Breed, mainCharacterDescent, half Cherokee]
-
A.
primaryCharacterChambersOf
Indicates that an entity serves as the main or central character within a specified set of chambers or rooms.
-
B.
descendedTo
Indicates that one entity has moved or traveled downward to reach the location or level of another entity.
-
C.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
D.
descentFrom
chosen
Indicates that one entity is a descendant of another, typically through a lineage or ancestral relationship.
-
E.
developmentCharacter
Indicates a relationship where one entity contributes to or influences the growth, formation, or evolution of another entity’s characteristics or qualities.
- 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37d6904008190a79ab30b6d9ccae9 |
completed | April 18, 2026, 12:47 p.m. |
| PD | Predicate disambiguation | batch_69e319bc73908190a0e38bc926b31f10 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.