Triple
T25643335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NS-16 mission |
E642889
|
entity |
| Predicate | crewRoleOfOliverDaemen |
P160265
|
FINISHED |
| Object | paying customer |
—
|
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: paying customer | Statement: [NS-16 mission, crewRoleOfOliverDaemen, paying customer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewRoleOfOliverDaemen Context triple: [NS-16 mission, crewRoleOfOliverDaemen, paying customer]
-
A.
roleOfOllieWilliams
Indicates the specific role, function, or capacity that Ollie Williams holds or performs in relation to another entity or context.
-
B.
directorCharacterOf
Indicates that a director is responsible for directing a particular character in a work (e.g., film, TV show, or play).
-
C.
directorCharacterName
Indicates that the specified name is the character name used by the director (or representing the director) within a work.
-
D.
roleInScoobyDoo
Indicates the specific function or character part an entity plays within the Scooby-Doo franchise or storyline.
-
E.
creditedRoleOf
Indicates that a particular role or position is formally acknowledged as being held or performed by a specific entity in a credit or attribution context.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f601f106a08190ad7b4537223dbd8c |
completed | May 2, 2026, 1:53 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f600be0de88190989611e952b03117 |
completed | May 2, 2026, 1:48 p.m. |
Created at: April 21, 2026, 5:48 p.m.