Triple
T26650636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandpiper Air |
E669040
|
entity |
| Predicate | foundedByCharacter |
P97495
|
FINISHED |
| Object | Joe Hackett |
—
|
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: Joe Hackett | Statement: [Sandpiper Air, foundedByCharacter, Joe Hackett]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedByCharacter Context triple: [Sandpiper Air, foundedByCharacter, Joe Hackett]
-
A.
foundedByFictional
chosen
Indicates that an entity (such as an organization, place, or group) was established or created by a fictional character or entity.
-
B.
foundedByCreatorOf
Indicates that an entity was founded by the same individual or group who created another specified entity.
-
C.
hasFounderCharacter
Indicates that an entity has a founder who possesses a specified character trait or set of personal qualities.
-
D.
possiblyFoundedBy
Indicates that an entity may have been founded or established by another entity, but this founding relationship is uncertain or not definitively confirmed.
-
E.
founded by
Indicates that an entity was established or created through the initiative, actions, or leadership of another entity.
- 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_69ee9d00eb5481908d6c6d0ada2f0c9a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 27, 2026, 2:32 a.m.