Triple
T25194865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irredeemable Ant-Man |
E630972
|
entity |
| Predicate | abilityFeatured |
P80690
|
FINISHED |
| Object | insect communication |
—
|
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: insect communication | Statement: [Irredeemable Ant-Man, abilityFeatured, insect communication]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abilityFeatured Context triple: [Irredeemable Ant-Man, abilityFeatured, insect communication]
-
A.
featuresIn
chosen
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.
-
B.
alsoFeatured
Indicates that an entity appears in addition to another primary entity within the same context, work, or presentation.
-
C.
recognizedFeature
Indicates that a particular feature has been identified and acknowledged as present or valid in relation to an entity or context.
-
D.
experienceFeature
Indicates that an entity undergoes, encounters, or makes use of a particular feature.
-
E.
designedFeature
Indicates that one entity is a feature or component intentionally planned, created, or specified by another entity as part of a design.
- 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_69e75a8a6d088190ba1e82a4345225e7 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46e12ea808190b08610a16810bc3a |
completed | May 1, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 12:46 p.m.