Triple
T20841435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | With cat-like tread |
E513111
|
entity |
| Predicate | performerRoleInWork |
P42172
|
FINISHED |
| Object | pirates |
—
|
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: pirates | Statement: [With cat-like tread, performerRoleInWork, pirates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performerRoleInWork Context triple: [With cat-like tread, performerRoleInWork, pirates]
-
A.
playsInRole
chosen
Indicates that an entity performs or appears in a specific role within a production, event, or context.
-
B.
performerCreditedAs
Indicates that a performer is associated with a work under a specific credited name or alias.
-
C.
actorRole
Indicates that an entity participates in an event or action in a specific capacity or function (such as performer, initiator, or responsible party).
-
D.
performerNotableWork
Indicates that a performer is significantly associated with or best known for a particular work (such as a performance, production, or recording).
-
E.
notableWorkRole
Indicates that a person’s role or position is specifically associated with the creation, performance, or contribution to a notable work.
- 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_69e0b4cf62a88190bbf92351e9e57259 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c34b17b88190b3290bd5100ad2ad |
completed | April 21, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a1f4f48190aa9fb4ef8f8aea5a |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:43 p.m.