Triple
T35419741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeffrey Skiles |
E1023747
|
entity |
| Predicate | hasNotableCoworker |
P120814
|
FINISHED |
| Object | Chesley Sullenberger |
E308427
|
NE 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: Chesley Sullenberger | Statement: [Jeffrey Skiles, hasNotableCoworker, Chesley Sullenberger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableCoworker Context triple: [Jeffrey Skiles, hasNotableCoworker, Chesley Sullenberger]
-
A.
hasColleagues
chosen
Indicates that one entity works alongside another in a professional or organizational context as colleagues.
-
B.
hasCompanionColleague
Indicates that one entity has another entity as a colleague who also serves as a companion or close associate.
-
C.
hasCollaborationIn
Indicates that two or more entities work together or jointly participate in a specific project, context, or domain.
-
D.
hasNotableConnectionToWork
Indicates that there is a significant or noteworthy relationship, influence, or association between an entity and a particular work.
-
E.
hasNotableCollaborationType
Indicates a specific kind or category of significant collaborative relationship that exists between entities.
- F. None of above.
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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3852da3f4c8190b8c3ab4884e3ed1e |
completed | June 21, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.