Triple
T29753184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vertical Alliance |
E752957
|
entity |
| Predicate | involvedStates |
P75246
|
FINISHED |
| Object | Zhao |
—
|
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: Zhao | Statement: [Vertical Alliance, involvedStates, Zhao]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedStates Context triple: [Vertical Alliance, involvedStates, Zhao]
-
A.
participatingState
Indicates that a state is taking part in, or is formally involved as a participant in, a specified event, process, or arrangement.
-
B.
affectedU.S.State
Indicates that a particular U.S. state is impacted or influenced by a specified event, condition, or entity.
-
C.
hasStateInvolved
chosen
Indicates that a particular state (as a political or administrative entity) participates in, is implicated in, or plays a role within a given situation, event, or relationship.
-
D.
nonParticipatingStates
Indicates that certain states are not taking part in a specified activity, agreement, or process.
-
E.
states
Indicates that an entity formally declares, expresses, or asserts a fact, opinion, or condition about another entity or situation.
- 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_69f0d62c84cc8190846f80ae04fdf8ec |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 28, 2026, 7:55 p.m.