Triple
T2934896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Green Bay |
E79240
|
entity |
| Predicate | isLocatedAt |
P40
|
FINISHED |
| Object | southern end of Green Bay |
—
|
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: southern end of Green Bay | Statement: [Port of Green Bay, isLocatedAt, southern end of Green Bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedAt Context triple: [Port of Green Bay, isLocatedAt, southern end of Green Bay]
-
A.
locatedIn
chosen
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
B.
agencyLocatedIn
Indicates that an agency is situated or based within a specific geographic or administrative location.
-
C.
isLocatedOn
Indicates that one entity exists at or is situated upon the surface or area of another entity.
-
D.
locatedInInstitutionType
Indicates that one entity is situated within, or belongs to, an institution of a specified type.
-
E.
locatedUnder
Indicates that one entity is positioned directly or generally beneath another entity in space.
- 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_69ad8b0fbab081908f6a61567c045d8d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad983c84688190aa7ed5b8091fb140 |
completed | March 8, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69ad96088fb481909976b436c2b729d9 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:56 p.m.