Triple
T15229224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albert |
E363953
|
entity |
| Predicate | subprefectureStatus |
P117653
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Albert, subprefectureStatus, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subprefectureStatus Context triple: [Albert, subprefectureStatus, no]
-
A.
subprefectureOf
Indicates that one administrative subprefecture is a subordinate division within and officially belongs to a larger governing region or prefecture.
-
B.
subprefecture
Indicates that an entity is a subprefecture (an administrative subdivision) of another administrative region or jurisdiction.
-
C.
subprefectureCapital
Indicates that one entity serves as the administrative capital or seat of government for a given subprefecture.
-
D.
hasPrefecturalOffice
Indicates that a given location or administrative unit contains or hosts an official prefectural government office.
-
E.
passesPrefecture
Indicates that a route, path, or entity traverses through or goes across a specified prefecture.
- F. None of above. chosen
Provenance (4 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0078ccdf48190b34eabd9e24e45a1 |
completed | April 15, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:12 a.m.