Triple
T25186740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broken Bow |
E630737
|
entity |
| Predicate | introducesCaptainOfEnterprise |
P160848
|
FINISHED |
| Object | Jonathan Archer |
—
|
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: Jonathan Archer | Statement: [Broken Bow, introducesCaptainOfEnterprise, Jonathan Archer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducesCaptainOfEnterprise Context triple: [Broken Bow, introducesCaptainOfEnterprise, Jonathan Archer]
-
A.
relativeTypeTo Leonard McCoy
Indicates the specific family or kinship relationship that an entity has to Leonard McCoy.
-
B.
assistantCaptain
Indicates that one entity serves as the assistant or deputy to another entity who holds the role of captain.
-
C.
laterCaptain
Indicates that one entity becomes the captain of something at a later time than another referenced captain or captaincy.
-
D.
captainSpecies
Indicates that a given species serves as the captain or commanding leader in relation to another entity or context.
-
E.
captain
Indicates that one entity serves as the leader or person in command of another entity, typically a team, group, or vessel.
- 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_69e75a8a6d088190ba1e82a4345225e7 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f60ac643108190ae81561267155791 |
completed | May 2, 2026, 2:31 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f606c15af88190958856a9e467b826 |
completed | May 2, 2026, 2:14 p.m. |
Created at: April 21, 2026, 12:44 p.m.