Triple
T37910025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Primrose Path |
E945659
|
entity |
| Predicate | hasMarjorieRambeauRole |
P204471
|
FINISHED |
| Object | Mamie Adams |
E2247847
|
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: Mamie Adams | Statement: [Primrose Path, hasMarjorieRambeauRole, Mamie Adams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMarjorieRambeauRole Context triple: [Primrose Path, hasMarjorieRambeauRole, Mamie Adams]
-
A.
characterPlayedByGalGadot
Indicates that a given character is portrayed or acted by Gal Gadot.
-
B.
roleInAvengersInfinityWar
Indicates that an entity has a specific role or appearance in the movie "Avengers: Infinity War."
-
C.
hasAvenger
Indicates that an entity is associated with or possesses an Avenger as part of its members, attributes, or related characters.
-
D.
roleInMarvelLore
Indicates the specific function, status, or narrative significance an entity holds within the Marvel universe’s storyline and mythology.
-
E.
marvelCinematicUniverseDebutFilm
Indicates the film in which an entity (such as a character or actor) first appeared within the Marvel Cinematic Universe.
- F. None of above. chosen
Provenance (5 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_69f76ef20bb0819088b5b6ceecb0b8fc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4117ecd7888190b4166c91cfa046bb |
completed | June 28, 2026, 12:47 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:20 p.m.