Triple
T16171348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wuchiapingian |
E392442
|
entity |
| Predicate | continentReference |
P121983
|
FINISHED |
| Object | defined from sections in South China |
—
|
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: defined from sections in South China | Statement: [Wuchiapingian, continentReference, defined from sections in South China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continentReference Context triple: [Wuchiapingian, continentReference, defined from sections in South China]
-
A.
continentType
Indicates that one entity is classified as a specific type or category of continent in relation to another entity.
-
B.
continentB
Indicates that the subject entity is a continent that contains or is associated with the object entity (such as a country, region, or location).
-
C.
continent
Indicates that one entity is a continent on which the other entity is geographically located or to which it belongs.
-
D.
continentScope
Indicates that something applies within, is limited to, or is defined at the level of a specific continent.
-
E.
continentSystem
Indicates a relationship where a continent is part of, or associated with, a particular planetary or geographic system.
- 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21eb7ab1481908fc35bfc8c56e5f2 |
completed | April 17, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:02 a.m.