Triple
T32558086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amnesty Bay, Maine |
E832144
|
entity |
| Predicate | fictionalHometownOf |
P107735
|
FINISHED |
| Object | Aquaman |
—
|
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: Aquaman | Statement: [Amnesty Bay, Maine, fictionalHometownOf, Aquaman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalHometownOf Context triple: [Amnesty Bay, Maine, fictionalHometownOf, Aquaman]
-
A.
fictionalBirthPlace
Indicates the fictional location where a character or entity is described as having been born within a narrative or imagined context.
-
B.
hasFictionalNearbyTown
Indicates that an entity is associated with a fictional town located in its vicinity or surrounding area.
-
C.
hasFictionalTownBasedOn
Indicates that a fictional town is modeled on, inspired by, or derived from a specific real-world town or location.
-
D.
cityOfFictionalResidence
chosen
Indicates that a fictional character or entity resides in, or is associated with living in, a particular city within a narrative or fictional context.
-
E.
basedInFictionalLocation
Indicates that an entity’s primary setting, origin, or operations occur in a fictional (non-real) location.
- 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_69f34926b9848190ace47d2dd0a0de7c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fddd373cdc8190be1b12e70e4deb1f |
completed | May 8, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69fddc6915a88190ad41e379aa3ede13 |
completed | May 8, 2026, 12:51 p.m. |
Created at: May 1, 2026, 1:03 a.m.