Triple
T38070243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth Eternals |
E950570
|
entity |
| Predicate | oftenInteractWith |
P23735
|
FINISHED |
| Object | Avengers |
—
|
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: Avengers | Statement: [Earth Eternals, oftenInteractWith, Avengers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenInteractWith Context triple: [Earth Eternals, oftenInteractWith, Avengers]
-
A.
typicalInteraction
Indicates the usual or most common way in which two entities interact or relate to each other.
-
B.
intendedAudienceInteraction
Indicates that one entity is the target group or audience with whom another entity is meant to interact or engage.
-
C.
oftenInvolvedWith
chosen
Indicates that one entity frequently participates in or is commonly associated with activities, events, or situations involving another entity.
-
D.
interactionWithHumans
Indicates a relationship where an entity engages in some form of contact, communication, or mutual influence with humans.
-
E.
interactionWithLiving
Indicates a relationship in which an entity engages in some form of contact, communication, or mutual influence with a living being.
- 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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
Created at: May 3, 2026, 4:21 p.m.