Triple
T29559477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stan S. Stanman |
E749998
|
entity |
| Predicate | roleWithGuybrush Threepwood |
P87456
|
FINISHED |
| Object | recurring salesman |
—
|
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: recurring salesman | Statement: [Stan S. Stanman, roleWithGuybrush Threepwood, recurring salesman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleWithGuybrush Threepwood Context triple: [Stan S. Stanman, roleWithGuybrush Threepwood, recurring salesman]
-
A.
playRoleIn
Indicates that an entity participates in or performs a specific function, character, or part within an event, context, or system.
-
B.
roleInGameplay
Indicates the specific function or responsibility an entity has within the context of gameplay or game mechanics.
-
C.
roleAtLuckyChap
Indicates that an entity holds or held a specific role or position at the organization LuckyChap.
-
D.
roleInRhyme
Indicates the specific function or part an entity plays within a rhyme, such as a character, object, or structural element of the rhyming text.
-
E.
playsAs
chosen
Indicates that one entity performs, portrays, or assumes the role, character, or persona of another entity.
- 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_69f0bd4919e48190942b2a13d5b97d03 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66d1c12688190a93492438e18b74e |
completed | May 2, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 5:18 p.m.