Triple
T11871084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yongkang District |
E282407
|
entity |
| Predicate | majorCharacteristic |
P72546
|
FINISHED |
| Object | suburban district |
—
|
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: suburban district | Statement: [Yongkang District, majorCharacteristic, suburban district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorCharacteristic Context triple: [Yongkang District, majorCharacteristic, suburban district]
-
A.
primaryCharacteristics
chosen
Indicates the main defining traits or features that most fundamentally characterize an entity.
-
B.
managementCharacteristic
Indicates a defining quality, style, or attribute associated with how something is managed or administered.
-
C.
missionCharacteristic
Indicates that a mission possesses a specific attribute, feature, or quality that characterizes its nature or execution.
-
D.
characterizedBy
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
E.
dataCharacteristic
Indicates that one entity specifies a property, attribute, or feature that characterizes a given piece of data.
- 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d39d2934819093b9f7006f45e5cb |
completed | April 10, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69d8bb272f88819090c37c944c5a60ab |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:43 p.m.