Triple
T21043387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emma Crawford Coffin Races |
E518384
|
entity |
| Predicate | teamRoles |
P75740
|
FINISHED |
| Object | one person as Emma in the coffin |
—
|
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: one person as Emma in the coffin | Statement: [Emma Crawford Coffin Races, teamRoles, one person as Emma in the coffin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamRoles Context triple: [Emma Crawford Coffin Races, teamRoles, one person as Emma in the coffin]
-
A.
teamSuccessRole
Indicates the role or contribution an entity has in achieving or influencing a team's success.
-
B.
portfolioRole
Indicates the specific function, capacity, or position an entity holds within a portfolio or collection of assets.
-
C.
unitRole
Indicates the functional role or purpose that a unit serves within a larger system or context.
-
D.
teamNumberRole
Indicates that a specific team, identified by its number, is associated with a particular role or function.
-
E.
roleOfPeopleOnIt
chosen
Indicates the specific roles or functions that people have in relation to a particular object, event, 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_69e0b50438e08190917e2538bb8bc034 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fcf1950081908ff9fe8719e1e81b |
completed | April 21, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf6728881908a2a43a5c8804a2a |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:19 p.m.