Triple
T7421568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perry |
E171258
|
entity |
| Predicate | importanceInWork |
P64796
|
FINISHED |
| Object | central character |
—
|
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: central character | Statement: [Perry, importanceInWork, central character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importanceInWork Context triple: [Perry, importanceInWork, central character]
-
A.
parentWorkSignificance
chosen
Indicates the degree of importance or influence that a parent work has on the related work or context.
-
B.
workImpact
Indicates that one entity’s work has an effect or influence on another entity, situation, or outcome.
-
C.
workRelatedTo
Indicates a relationship where one entity’s work, tasks, or professional activities are connected, associated, or relevant to those of another entity.
-
D.
positionInWork
Indicates the specific role, rank, or placement an entity holds within a larger work or structured composition.
-
E.
usedInWork
Indicates that something (such as a concept, method, material, or component) is employed or applied within a particular work, project, or creation.
- 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_69c68a625d048190af70eb8b63bec5a0 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2ebc520819087cfc2eb9dda0e17 |
completed | March 27, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c6f03648d08190b862d07fef71210c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:11 p.m.