Triple
T36571788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond |
E902138
|
entity |
| Predicate | titleInPlay |
P200908
|
FINISHED |
| Object | Earl of Richmond |
—
|
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: Earl of Richmond | Statement: [Richmond, titleInPlay, Earl of Richmond]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleInPlay Context triple: [Richmond, titleInPlay, Earl of Richmond]
-
A.
playTitle
Indicates the title or name assigned to a play in a relationship between a play entity and its textual label.
-
B.
titleContenders
Indicates that the related entities are competing or in strong contention for a particular title or championship.
-
C.
titleOfTitle
Indicates that one title is the title of another title (e.g., a sub-title or alternate title associated with a primary title).
-
D.
titleInPretence
Indicates that an entity holds a specific title or role within a fictional, staged, or pretended context rather than in reality.
-
E.
playWithinPlayTitle
Indicates that one play is presented as a play within another play, and this predicate gives the title of that embedded play.
- F. None of above. chosen
Provenance (4 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffb82be8148190a1c870d467a28c80 |
completed | May 9, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69ffb7bbd550819094052e9a0d0ae320 |
completed | May 9, 2026, 10:39 p.m. |
| PDg | Predicate description generation | batch_69ffb82b40788190bf401344a3f288dd |
completed | May 9, 2026, 10:41 p.m. |
Created at: May 3, 2026, 4:11 p.m.