Triple
T26029812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Đại Cồ Việt |
E647396
|
entity |
| Predicate | tributaryRelation |
P144467
|
FINISHED |
| Object | Song dynasty China |
—
|
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: Song dynasty China | Statement: [Đại Cồ Việt, tributaryRelation, Song dynasty China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tributaryRelation Context triple: [Đại Cồ Việt, tributaryRelation, Song dynasty China]
-
A.
hasTributaryRelationsWith
Indicates that one entity maintains a tributary relationship with another, typically involving regular payments or offerings in exchange for protection, favor, or acknowledgment of superiority.
-
B.
isHeadwaterTributaryOf
Indicates that one watercourse is a source or upstream tributary that feeds into another watercourse.
-
C.
tributary
Indicates that one watercourse flows into and feeds another, contributing its water to a larger stream, river, or lake.
-
D.
hasTributaryRelation
chosen
Indicates a relationship where one entity serves as a tributary, paying regular tribute or acknowledging subordination to another entity.
-
E.
isNaturalTributaryOf
Indicates that one watercourse flows naturally into another, contributing its water as a tributary without artificial diversion.
- 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605ee5ba88190bc99652ac24b69b0 |
completed | May 2, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 9:06 a.m.