Triple
T33914136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superman #13 |
E869402
|
entity |
| Predicate | featuresPhotographerCharacter |
P12333
|
FINISHED |
| Object | Jimmy Olsen |
E248309
|
NE 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: Jimmy Olsen | Statement: [Superman #13, featuresPhotographerCharacter, Jimmy Olsen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresPhotographerCharacter Context triple: [Superman #13, featuresPhotographerCharacter, Jimmy Olsen]
-
A.
photographerProfession
Indicates that one entity has the profession or occupation of being a photographer.
-
B.
photographer
chosen
Indicates that one entity takes photographs of another entity, typically in a professional or intentional capacity.
-
C.
featuresCharacterWith
Indicates that one entity (such as a work or product) includes or presents a particular character as part of its content.
-
D.
portraitSpecialization
Indicates that one entity specializes in creating or working with portraits, distinguishing a focused area of expertise within a broader artistic or professional domain.
-
E.
featuresFigureOf
Indicates that one entity includes or presents another entity as a figure, illustration, or visual element.
- F. None of above.
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_69f3499869bc8190b6c33a81686af226 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0248062e608190aae1afdae38d2e5a |
completed | May 11, 2026, 9:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36ae362068819088c4a3e396bc510f |
completed | June 20, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_6a02465a0d38819084c3a6813fb943fc |
completed | May 11, 2026, 9:12 p.m. |
Created at: May 1, 2026, 1:48 a.m.