Triple
T19481888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drowned Meadow |
E487404
|
entity |
| Predicate | presentDayVillageType |
P126753
|
FINISHED |
| Object | incorporated village |
—
|
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: incorporated village | Statement: [Drowned Meadow, presentDayVillageType, incorporated village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentDayVillageType Context triple: [Drowned Meadow, presentDayVillageType, incorporated village]
-
A.
isVillage
chosen
Indicates that the subject entity is classified as a village, typically a small human settlement or community.
-
B.
presentDayMunicipality
Indicates that one entity is the current-day municipality encompassing or corresponding to the area or jurisdiction of another (typically historical) entity.
-
C.
hasVillage
Indicates that an entity possesses, contains, or is associated with a village.
-
D.
presentDayTownName
Indicates that the object is the current or modern-day town name corresponding to the subject.
-
E.
capitalVillage
Indicates that a village serves as the administrative or political capital of a specified region or entity.
- 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_69d8e8d924388190b847cb15bb3d0aff |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6343ab16481909b508ba0a08ea191 |
completed | April 20, 2026, 2:12 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7883308190b73912a71a35a835 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.