Triple
T4455801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reundorf |
E97718
|
entity |
| Predicate | administrativeStatusWithinTown |
P37705
|
FINISHED |
| Object | village subdivision |
—
|
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: village subdivision | Statement: [Reundorf, administrativeStatusWithinTown, village subdivision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeStatusWithinTown Context triple: [Reundorf, administrativeStatusWithinTown, village subdivision]
-
A.
administrativeStatusCurrent
Indicates the current administrative status or condition of an entity within a governing or managing system.
-
B.
hasTownStatus
Indicates that an entity possesses the legal or administrative status of being recognized as a town.
-
C.
isMunicipalStatus
chosen
Indicates that an entity possesses a specific legally defined municipal status or classification within a governmental or administrative system.
-
D.
administrativeStatusUnderRome
Indicates the type or level of administrative control or governance an entity was subject to within the Roman political system.
-
E.
cityStatusUntil
Indicates the period up to a specified time during which a place holds or held a particular city status.
- 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_69b3454777808190b78aa9047ba1f018 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355f79ca481909338dda9f4f7171f |
completed | March 13, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69b34f649df081909d3cc2f6a1b8f282 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:33 p.m.