Triple
T30550365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The King Is Dead |
E777539
|
entity |
| Predicate | featuresWorkWithinWork |
P51454
|
FINISHED |
| Object | The King and I |
—
|
NE NERFINISHED |
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: The King and I | Statement: [The King Is Dead, featuresWorkWithinWork, The King and I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresWorkWithinWork Context triple: [The King Is Dead, featuresWorkWithinWork, The King and I]
-
A.
workWithin
Indicates that one entity performs its activities or duties inside the boundaries, scope, or context defined by another entity.
-
B.
featuresWorkType
Indicates that an entity includes, supports, or is characterized by a particular type or category of work.
-
C.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another entity.
-
D.
workFeatured
chosen
Indicates that one work is highlighted, showcased, or given special prominence within a particular context, collection, or presentation.
-
E.
works in
Indicates that one entity performs their job or professional activities within the organization, location, or context represented by 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_69f2249e19108190a458ab446096bf22 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a000a1d8fa88190a1d82ac746565c48 |
completed | May 10, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_6a0008b26eb88190ae03b2309a614774 |
completed | May 10, 2026, 4:25 a.m. |
Created at: April 29, 2026, 8:20 p.m.