Triple
T33093729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Howard Silk |
E846851
|
entity |
| Predicate | counterpartVersion |
P202459
|
FINISHED |
| Object | Prime world Howard Silk |
—
|
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: Prime world Howard Silk | Statement: [Howard Silk, counterpartVersion, Prime world Howard Silk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: counterpartVersion Context triple: [Howard Silk, counterpartVersion, Prime world Howard Silk]
-
A.
counterpartService
Indicates that one service functions as the corresponding or matching service to another within a defined relationship or context.
-
B.
counterpartRelation
Indicates a reciprocal relationship where two entities serve as corresponding or equivalent counterparts to each other in a given context.
-
C.
hasCounterpart
Indicates that one entity corresponds to, matches, or serves as an equivalent or parallel version of another entity.
-
D.
counterpartTerm
Indicates that one term serves as a corresponding or equivalent term to another within a specific relational or comparative context.
-
E.
counterpartEnglishName
Indicates that an entity has a corresponding counterpart whose name is given in English.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a00818b20a881909fbf3bb33dcf7029 |
completed | May 10, 2026, 1 p.m. |
| PD | Predicate disambiguation | batch_6a0080f76f588190a933238861243d1a |
completed | May 10, 2026, 12:58 p.m. |
| PDg | Predicate description generation | batch_6a00818a671c819086d487dd5a5ba5d7 |
completed | May 10, 2026, 1 p.m. |
Created at: May 1, 2026, 1:26 a.m.