Triple
T34566863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lilliput |
E887514
|
entity |
| Predicate | rivalCountry |
P22658
|
FINISHED |
| Object | Blefuscu |
—
|
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: Blefuscu | Statement: [Lilliput, rivalCountry, Blefuscu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rivalCountry Context triple: [Lilliput, rivalCountry, Blefuscu]
-
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.
rivalryBetweenNationality2
Indicates a competitive or adversarial relationship existing between two different nationalities.
-
C.
primaryOpposingCountry
Indicates that one country is the main or principal adversary or opponent of another country in a conflict, rivalry, or opposition.
-
D.
opponentNationality
Indicates that the related entity is the country or nationality of the opponent in a competitive or adversarial context.
-
E.
biddingRivalCountry
Indicates a relationship where one country competes with another in placing bids, typically for the same contract, project, or opportunity.
- 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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f720671b2881909b5f85ea73a7a8fa |
completed | May 3, 2026, 10:16 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:02 a.m.