Triple
T2855259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fedallah |
E63183
|
entity |
| Predicate | questInvolvedIn |
P43670
|
FINISHED |
| Object | Ahab’s hunt for Moby Dick |
—
|
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: Ahab’s hunt for Moby Dick | Statement: [Fedallah, questInvolvedIn, Ahab’s hunt for Moby Dick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: questInvolvedIn Context triple: [Fedallah, questInvolvedIn, Ahab’s hunt for Moby Dick]
-
A.
isSoughtBy
Indicates that one entity is actively being searched for, pursued, or desired by another entity.
-
B.
fortInvolved
Indicates that a fort is involved or participates in a particular event, action, or relationship between entities.
-
C.
hasMemberInvolvedIn
Indicates that a group or collective entity has at least one of its members participating in or engaged with a specified activity, event, or situation.
-
D.
oftenInvolvedWith
Indicates that one entity frequently participates in or is commonly associated with activities, events, or situations involving another entity.
-
E.
investigatedBy
Indicates that an entity is the subject of an investigation carried out by another entity.
- 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.