Triple
T23100018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superman comics |
E575998
|
entity |
| Predicate | featureConcept |
P24015
|
FINISHED |
| Object | secret identity |
—
|
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: secret identity | Statement: [Superman comics, featureConcept, secret identity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featureConcept Context triple: [Superman comics, featureConcept, secret identity]
-
A.
featuredConcept
chosen
Indicates that one concept is highlighted or given special prominence relative to others in a particular context.
-
B.
featuresCreator
Indicates that an entity prominently presents, highlights, or showcases a particular creator as a key associated party.
-
C.
featureDesignation
Indicates the specific label or name assigned to a feature to distinguish it from other features.
-
D.
featureType
Indicates the specific kind or category of feature that characterizes or distinguishes an entity.
-
E.
featuresIn
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
- 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_69e245c060b48190a9bd61a47a16db17 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18de81060819084ab618f05aae583 |
completed | April 29, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_69ef89e5ce748190b2c3ac3843484127 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:58 p.m.