Triple
T4330989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flight 5 |
E96746
|
entity |
| Predicate | hasContributorRole |
P45538
|
FINISHED |
| Object | editor |
—
|
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: editor | Statement: [Flight 5, hasContributorRole, editor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContributorRole Context triple: [Flight 5, hasContributorRole, editor]
-
A.
hasContributionFrom
Indicates that something (such as a work, project, or outcome) is created, influenced, or supported in part by a specified contributor.
-
B.
collaboratorRole
chosen
Indicates the specific function, position, or capacity in which one collaborator participates in a shared activity or project with another.
-
C.
hasOrganizationalRole
Indicates that an entity holds a specific role, position, or function within an organization.
-
D.
hasNotableRoleIn
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
-
E.
hasAuthorRelationship
Indicates a relationship where one entity serves as the author or creator of another entity (such as a work, document, or resource).
- 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_69b34542fd908190b11b08faad8decfd |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3514c39748190900e13e70ed8848c |
completed | March 12, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69b34f4e13fc8190a42c519f37959d27 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:13 p.m.