Triple
T2855245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fedallah |
E63183
|
entity |
| Predicate | relationshipToAhab |
P43668
|
FINISHED |
| Object | spiritual counselor |
—
|
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: spiritual counselor | Statement: [Fedallah, relationshipToAhab, spiritual counselor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToAhab Context triple: [Fedallah, relationshipToAhab, spiritual counselor]
-
A.
relationshipToHuckFinn
Indicates the specific type of personal or social relationship an entity has to Huck Finn.
-
B.
relationshipToHuck
Indicates the specific type of personal or social relationship that one entity has with Huck.
-
C.
poseidonRelation
Indicates a mythological or symbolic relationship involving Poseidon, such as kinship, patronage, or influence over another entity.
-
D.
relationshipToMissWatson
Indicates the type or nature of a person's relational connection to Miss Watson (e.g., familial, social, or other defined relationship).
-
E.
hasProtagonistRelationship
Indicates that there exists a central, story-driving relationship involving the protagonist and another entity within a narrative.
- 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_69ab4c407c408190857d25e027155ce9 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf60852c8190b66c8719c63a723e |
completed | March 7, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69abdd10aef88190b750aae07e7df4dc |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abdee94c2081908e5075e87e70780a |
completed | March 7, 2026, 8:16 a.m. |
Created at: March 6, 2026, 10:02 p.m.