Triple
T26029980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Song–Đại Cồ Việt War |
E647402
|
entity |
| Predicate | kingdomInvolved |
P20193
|
FINISHED |
| Object | Đại Cồ Việt |
—
|
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: Đại Cồ Việt | Statement: [Song–Đại Cồ Việt War, kingdomInvolved, Đại Cồ Việt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kingdomInvolved Context triple: [Song–Đại Cồ Việt War, kingdomInvolved, Đại Cồ Việt]
-
A.
kingdomAssociatedWith
chosen
Indicates a relationship where something is connected or related to a particular kingdom, such as belonging to, originating from, or being governed by that kingdom.
-
B.
kingdom
Indicates that an entity is classified within a particular biological kingdom in a taxonomic hierarchy.
-
C.
kingdomsIncluded
Indicates that one or more kingdoms are contained within, or form part of, a larger political or territorial entity.
-
D.
mentionsKingdom
Indicates that one entity explicitly refers to or brings up the topic of a kingdom in relation to another entity.
-
E.
clientKingdomOf
Indicates a relationship where one kingdom is politically subordinate or tributary to another, more powerful kingdom while retaining limited internal autonomy.
- 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.