Triple
T18662852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Billie the oiler |
E456244
|
entity |
| Predicate | relationshipToCrew |
P132195
|
FINISHED |
| Object | shares labor equally |
—
|
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: shares labor equally | Statement: [Billie the oiler, relationshipToCrew, shares labor equally]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToCrew Context triple: [Billie the oiler, relationshipToCrew, shares labor equally]
-
A.
relationshipToHeistCrew
Indicates the specific role, connection, or association an entity has with a particular heist crew.
-
B.
relationshipToHermesCrew
Indicates the specific type of personal or professional relationship an entity has with the Hermes crew.
-
C.
hasCrewRole
Indicates that an entity serves in a specific role or position within a crew associated with another entity.
-
D.
refersToCrew
Indicates that one entity makes reference to, is associated with, or pertains to a specific crew or group of crew members.
-
E.
followsCrewOf
Indicates that one entity follows, tracks, or stays close behind the crew associated with another entity.
- 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_69d8d38f72b4819090a935175d9ca8af |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5508c0d088190bef46fb3a3001f10 |
completed | April 19, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484133ee48190a80f1889d79f34c9 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:48 a.m.