Triple
T32011049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | We’re Here |
E817401
|
entity |
| Predicate | homePortInFiction |
P3150
|
FINISHED |
| Object | Gloucester, Massachusetts |
—
|
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: Gloucester, Massachusetts | Statement: [We’re Here, homePortInFiction, Gloucester, Massachusetts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homePortInFiction Context triple: [We’re Here, homePortInFiction, Gloucester, Massachusetts]
-
A.
homeportInUniverse
Indicates that an entity’s designated home port or primary base of operations is located within a specified universe.
-
B.
basedInFictionalWorkLocation
Indicates that an entity’s location or setting is situated within a fictional place as depicted in a specific creative work.
-
C.
hostsFictional
Indicates that one entity serves as the setting, platform, or environment in which a fictional character, event, or work is situated or presented.
-
D.
basedInFictionalLocation
Indicates that an entity’s primary setting, origin, or operations occur in a fictional (non-real) location.
-
E.
homePort
chosen
Indicates that a vessel or mobile entity is based at, registered to, or primarily operates from a particular port or harbor.
- 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_69f348f9e5d081908cc3f57c4942af52 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b42f7b5081908dae0678c4cd6888 |
completed | May 3, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:15 a.m.