Triple
T9885175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neville Sinclair |
E180911
|
entity |
| Predicate | worksInUniverseAs |
P58964
|
FINISHED |
| Object | leading man actor |
—
|
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: leading man actor | Statement: [Neville Sinclair, worksInUniverseAs, leading man actor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksInUniverseAs Context triple: [Neville Sinclair, worksInUniverseAs, leading man actor]
-
A.
hasInUniverseRole
chosen
Indicates that an entity holds or performs a specific role or function within a particular fictional or defined universe.
-
B.
developerOfWorkAppearingIn
Indicates that one entity is the creator or developer of a work in which another entity appears or is featured.
-
C.
worksWith
Indicates that two entities collaborate or perform tasks together in a shared work-related context.
-
D.
hasFictionalWork
Indicates that one entity is the creator, owner, or source of a fictional work associated with another entity.
-
E.
genreOfWorkCharacterIsIn
Indicates the specific genre of the creative work in which a given character appears.
- 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_69ca828082cc8190a40f8d299caa6545 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb45549488190833200977d558e47 |
completed | April 2, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69cd1d810ed48190a252b70e9390c8f3 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:38 p.m.