Triple
T12307714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hive (MCU) |
E293395
|
entity |
| Predicate | transportedToEarthBy |
P104366
|
FINISHED |
| Object | S.H.I.E.L.D. portal mission |
—
|
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: S.H.I.E.L.D. portal mission | Statement: [Hive (MCU), transportedToEarthBy, S.H.I.E.L.D. portal mission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportedToEarthBy Context triple: [Hive (MCU), transportedToEarthBy, S.H.I.E.L.D. portal mission]
-
A.
removedFromEarthBy
Indicates that an entity was taken away or extracted from Earth by another agent or process.
-
B.
leavesEarthWith
Indicates that one entity departs from Earth together with another entity, accompanying them in leaving the planet.
-
C.
landedOnBy
Indicates that one entity has come down to rest upon or make contact with the surface of another entity.
-
D.
exploredByAstronaut
Indicates that something has been examined, traveled through, or investigated by an astronaut.
-
E.
wasTransportedTo
Indicates that an entity was moved or carried from one location to another, resulting in its arrival at the specified destination.
- 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec02c008190a56aae60a3d9eff6 |
completed | April 10, 2026, 6:17 p.m. |
| PDg | Predicate description generation | batch_69d93f607a88819089e89fd263ae9937 |
completed | April 10, 2026, 6:20 p.m. |
Created at: April 8, 2026, 9:53 p.m.