Triple
T30694050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Masconomo |
E781407
|
entity |
| Predicate | hasNamePreservedIn |
P149843
|
FINISHED |
| Object | regional geography |
—
|
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: regional geography | Statement: [Masconomo, hasNamePreservedIn, regional geography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamePreservedIn Context triple: [Masconomo, hasNamePreservedIn, regional geography]
-
A.
namePreservedIn
chosen
Indicates that an entity’s name has been maintained or carried over unchanged within another entity or context.
-
B.
hasPreserved
Indicates that one entity has kept another entity intact, unchanged, or maintained in its original or functional state over time.
-
C.
isPreservedBy
Indicates that something remains unchanged, intact, or maintained as it is due to the action or influence of a particular agent or process.
-
D.
hasOriginalNameOf
Indicates that one entity is the original or earlier name from which another entity’s current or later name is derived.
-
E.
hasNameBeforeChange
Indicates that an entity is associated with the name it had prior to some change or renaming event.
- 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_69f224ab24e08190991d6edb6df58e8b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: April 29, 2026, 8:33 p.m.