Triple
T28075886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Langya Commandery |
E709539
|
entity |
| Predicate | modernAreaIncludes |
P8991
|
FINISHED |
| Object | Linyi |
—
|
NE NERFINISHED |
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: Linyi | Statement: [Langya Commandery, modernAreaIncludes, Linyi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernAreaIncludes Context triple: [Langya Commandery, modernAreaIncludes, Linyi]
-
A.
modernAreaCorrespondsTo
Indicates that a historical or former area is associated with, or has its equivalent in, a specified modern geographic or administrative area.
-
B.
includesAreaOf
Indicates that one entity encompasses or contains the spatial extent or area covered by another entity.
-
C.
modernTerritoryIncludes
chosen
Indicates that the geographic area of one modern political or administrative territory fully or partially contains the geographic area of another.
-
D.
includesAreaType
Indicates that one entity encompasses or contains another entity of a specified area type within its scope or boundaries.
-
E.
hasAreaType
Indicates that an entity is associated with a specific kind or classification of area (e.g., urban, rural, coastal).
- 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.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, 8:48 p.m.