Triple
T31529659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qays |
E804441
|
entity |
| Predicate | rivalBloc |
P22658
|
FINISHED |
| Object | Yaman (southern Arabs) |
—
|
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: Yaman (southern Arabs) | Statement: [Qays, rivalBloc, Yaman (southern Arabs)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rivalBloc Context triple: [Qays, rivalBloc, Yaman (southern Arabs)]
-
A.
rivalOf
chosen
Indicates a relationship in which two entities compete against or oppose each other, often seeking advantage in the same domain or objective.
-
B.
rivalParty
Indicates that one party is in competition or opposition with another party, often pursuing conflicting goals or interests.
-
C.
rivalSuperstate
Indicates a relationship where one superstate is considered a rival or adversarial counterpart to another superstate.
-
D.
rivalryBasis
Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
-
E.
opponentCapitalOf
Indicates that one entity is the capital city of a political or territorial unit that is considered an opponent or adversary of another referenced 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10 p.m.