Triple
T29929894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Passing Ships |
E760183
|
entity |
| Predicate | hasPersonnelRole |
P27764
|
FINISHED |
| Object | Andrew Hill – piano |
—
|
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: Andrew Hill – piano | Statement: [Passing Ships, hasPersonnelRole, Andrew Hill – piano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPersonnelRole Context triple: [Passing Ships, hasPersonnelRole, Andrew Hill – piano]
-
A.
hasOrganizationalRole
Indicates that an entity holds a specific role, position, or function within an organization.
-
B.
leadershipRoleOn
Indicates that one entity holds a leadership position or role with respect to another entity.
-
C.
roleInPersonnelMatters
Indicates that one entity has a specific function, authority, or involvement in managing or deciding personnel-related matters concerning another entity.
-
D.
personnelType
Indicates the classification or role category assigned to a person within an organization or system.
-
E.
hasNotableRoleIn
chosen
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
- 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_69f224631674819080c8d089674f9f4f |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: April 29, 2026, 6:17 p.m.