Triple
T30616121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawk and Dove |
E779320
|
entity |
| Predicate | laterHawkRealName |
P198756
|
FINISHED |
| Object | Holly Granger |
—
|
NE NERFINISHED |
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: Holly Granger | Statement: [Hawk and Dove, laterHawkRealName, Holly Granger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterHawkRealName Context triple: [Hawk and Dove, laterHawkRealName, Holly Granger]
-
A.
laterCaptain
Indicates that one entity becomes the captain of something at a later time than another referenced captain or captaincy.
-
B.
Jack Hively
Indicates a relationship or action involving the person named Jack Hively, such as authorship, direction, or participation in a work or event.
-
C.
notableAfterguardMember
Indicates that an individual is recognized as a prominent or distinguished member of a ship’s afterguard (the senior or aft-deck crew).
-
D.
laterWielder
Indicates that one entity becomes the wielder or user of an object or power after another entity who wielded it earlier.
-
E.
laterTitleHolder
Indicates that one entity is a subsequent holder of a particular title or position previously held 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff0491409c8190be40f633a58da0b1 |
completed | May 9, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69ff040bb5cc81909534c7eee85d5e90 |
completed | May 9, 2026, 9:53 a.m. |
| PDg | Predicate description generation | batch_69ff04901ab081908b68563836fcdc99 |
completed | May 9, 2026, 9:55 a.m. |
Created at: April 29, 2026, 8:26 p.m.