Triple
T30770633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Đàng Trong |
E783512
|
entity |
| Predicate | historicalCounterpart |
P114259
|
FINISHED |
| Object | Đàng Ngoài |
—
|
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: Đàng Ngoài | Statement: [Đàng Trong, historicalCounterpart, Đàng Ngoài]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalCounterpart Context triple: [Đàng Trong, historicalCounterpart, Đàng Ngoài]
-
A.
historicalHeir
Indicates that one entity is recognized as the successor or inheritor of another in a historical or dynastic context.
-
B.
historicalReference
Indicates that one entity refers to, cites, or alludes to another entity from an earlier time or historical context.
-
C.
sameHistoricalFigureAs
Indicates that two entities refer to the same historical person, treating them as different representations or records of one individual.
-
D.
historicalAlignmentOf
chosen
Indicates a relationship where entities share or are compared based on their positions, roles, or associations within a specific historical context or period.
-
E.
historicallyLinked
Indicates that two entities are connected through a shared or related historical event, period, or development.
- 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff17be6ad48190963206f2619b1b28 |
completed | May 9, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69ff1724ba24819092c928fcbcb286ec |
completed | May 9, 2026, 11:14 a.m. |
Created at: April 29, 2026, 8:40 p.m.