Triple
T26878049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanto |
E676807
|
entity |
| Predicate | administrativeClassificationBeforeMerger |
P98304
|
FINISHED |
| Object | town |
—
|
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: town | Statement: [Tanto, administrativeClassificationBeforeMerger, town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeClassificationBeforeMerger Context triple: [Tanto, administrativeClassificationBeforeMerger, town]
-
A.
governingBodyBeforeMerger
Indicates that one entity functioned as the governing body of another entity prior to a merger event.
-
B.
affiliationBeforeMerger
Indicates that an entity was affiliated with another entity prior to a merger event involving one or both of them.
-
C.
constitutionalStatusBeforeMerger
Indicates the constitutional or legal status an entity held prior to being merged into another entity or structure.
-
D.
censusSubdivisionTypeBeforeMerger
chosen
Indicates the type or classification of a census subdivision that it held prior to being merged into another administrative unit.
-
E.
governingBodyAtMerger
Indicates the organization or authority that served as the governing body of an entity at the time it merged with another 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_69eee9bb44988190b6e11652d028bc59 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 27, 2026, 5:37 a.m.