Triple
T922503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tar Baby |
E19912
|
entity |
| Predicate | featuresCharacterDescription |
P662
|
FINISHED |
| Object | mysterious drifter |
—
|
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: mysterious drifter | Statement: [Tar Baby, featuresCharacterDescription, mysterious drifter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresCharacterDescription Context triple: [Tar Baby, featuresCharacterDescription, mysterious drifter]
-
A.
featuresText
Indicates that an entity includes or presents a specific piece of text as one of its characteristics or contents.
-
B.
character1
Indicates that the subject is identified as the first or primary character in a narrative or context.
-
C.
character2
Indicates that a second character entity is involved in the relationship or context defined by the predicate.
-
D.
characterizedBy
chosen
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
E.
featuresDeity
Indicates that a work, object, or context prominently includes, depicts, or centers around a particular deity.
- 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_69a493a099788190a696d9d8408cbaf4 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b314f6fc81908a3ccc2e741e3c2b |
completed | March 1, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69a4b295b02481908e5f53bfcb83cc94 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.