Triple
T14719908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danvers Osborn |
E345783
|
entity |
| Predicate | toponymLinkStatus |
P71313
|
FINISHED |
| Object | controversial |
—
|
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: controversial | Statement: [Danvers Osborn, toponymLinkStatus, controversial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toponymLinkStatus Context triple: [Danvers Osborn, toponymLinkStatus, controversial]
-
A.
toponymStatus
chosen
Indicates the status or classification of a place name within a geographic naming or toponymic system.
-
B.
toponymRefersTo
Indicates that a place name (toponym) designates or refers to a specific geographic entity or location.
-
C.
hasToponymy
Indicates a relationship where one entity possesses or is associated with the system, study, or set of place names (toponyms) of another entity.
-
D.
toponymSourceFor
Indicates that one entity serves as the origin, basis, or source from which another entity’s place name (toponym) is derived.
-
E.
hasToponymicUse
Indicates that a term or name is used as a toponym, i.e., as a place name or geographic designation.
- 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb98823408190b4b58a4c4a3fa3a3 |
completed | April 14, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69de657e174481909da0437556334a04 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:29 a.m.