Triple
T34284763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PHMNL |
E879701
|
entity |
| Predicate | identifiesTypeOfLocation |
P134880
|
FINISHED |
| Object | seaport |
—
|
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: seaport | Statement: [PHMNL, identifiesTypeOfLocation, seaport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifiesTypeOfLocation Context triple: [PHMNL, identifiesTypeOfLocation, seaport]
-
A.
subjectLocationType
chosen
Indicates the type or category of location associated with the subject in the relationship.
-
B.
placeType
Indicates the type or category of place associated with an entity (e.g., city, park, building).
-
C.
regionTypeOfPlace
Indicates that a place belongs to or is categorized under a specific type of geographic or administrative region.
-
D.
settingLocationType
Indicates the type or category of location in which an event, action, or situation takes place.
-
E.
cityTypeLocation
Indicates that a location is classified as a specific type of city (e.g., capital, metropolitan, coastal).
- 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_69f349b5f6648190b9420d94a4cd16e0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f72ad38a208190b4bdc828297f86ad |
completed | May 3, 2026, 11 a.m. |
| PD | Predicate disambiguation | batch_69f72a0243988190a43b8ea22457cd30 |
completed | May 3, 2026, 10:57 a.m. |
Created at: May 1, 2026, 1:57 a.m.