Triple
T5695488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhengzhou |
E125528
|
entity |
| Predicate | nearbyAncientCapital |
P55312
|
FINISHED |
| Object | Shang dynasty ruins at Zhengzhou Shang City |
—
|
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: Shang dynasty ruins at Zhengzhou Shang City | Statement: [Zhengzhou, nearbyAncientCapital, Shang dynasty ruins at Zhengzhou Shang City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyAncientCapital Context triple: [Zhengzhou, nearbyAncientCapital, Shang dynasty ruins at Zhengzhou Shang City]
-
A.
hasNearbyAncientCity
chosen
Indicates that one entity is located close to another entity that is classified as an ancient city.
-
B.
ancientCity
Indicates that the subject is a historically old or long-established city, typically originating from ancient times.
-
C.
nearbyRomanTown
Indicates that one location is geographically close to a town that existed during the Roman period.
-
D.
majorAncientCity
Indicates that a location functioned as a principal or highly significant city during ancient historical periods.
-
E.
regionCapitalNearby
Indicates that a capital city of a region is located close to the referenced place or 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_69c0082bb19c8190823a4facd3cba79b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c0e0408190ab6c3cd3f907e80f |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:45 p.m.