Triple
T29082464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meredith Quill |
E734015
|
entity |
| Predicate | fictionalLocationOfBirth |
P49113
|
FINISHED |
| Object | Missouri |
—
|
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: Missouri | Statement: [Meredith Quill, fictionalLocationOfBirth, Missouri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalLocationOfBirth Context triple: [Meredith Quill, fictionalLocationOfBirth, Missouri]
-
A.
fictionalBirthPlace
chosen
Indicates the fictional location where a character or entity is described as having been born within a narrative or imagined context.
-
B.
basedInFictionalLocation
Indicates that an entity’s primary setting, origin, or operations occur in a fictional (non-real) location.
-
C.
basedInFictionalWorkLocation
Indicates that an entity’s location or setting is situated within a fictional place as depicted in a specific creative work.
-
D.
fictionalCountryLocation
Indicates that a fictional country is located within, or geographically associated with, a specified place or region.
-
E.
bornInFictionalSetting
Indicates that a character’s birth occurs within a fictional, imagined, or non-real-world setting.
- 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_69f05b0c0f28819086eae6e84f2ae472 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: April 28, 2026, 10:56 a.m.