Triple
T36119368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Collinwood |
E1044700
|
entity |
| Predicate | productionExteriorLocation |
P143383
|
FINISHED |
| Object | Newport, Rhode Island |
—
|
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: Newport, Rhode Island | Statement: [Collinwood, productionExteriorLocation, Newport, Rhode Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productionExteriorLocation Context triple: [Collinwood, productionExteriorLocation, Newport, Rhode Island]
-
A.
hasExteriorSetLocation
chosen
Indicates that an entity’s exterior is situated at, or associated with, a specific location or setting.
-
B.
exteriorBasedOn
Indicates that the exterior of one entity is designed, derived, or determined based on the characteristics or specifications of another entity.
-
C.
exteriorFeature
Indicates a relationship where one entity serves as an external or outward-facing feature, element, or characteristic of another entity.
-
D.
oftenLocatedAt
Indicates that an entity is frequently or commonly found at, or associated with being in, a particular location.
-
E.
plantLocation
Indicates the location where a plant is situated, grown, or found.
- 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_69f76e356c908190abc6ca1e6a05b011 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fefb15220081908da36aac386fa582 |
completed | May 9, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69fefa8e8ad48190a723fed81e9d64d0 |
completed | May 9, 2026, 9:12 a.m. |
Created at: May 3, 2026, 4:08 p.m.