Triple
T20566337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zilu |
E504974
|
entity |
| Predicate | birthPlace |
P1
|
FINISHED |
| Object | state of Lu |
—
|
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: state of Lu | Statement: [Zilu, birthPlace, state of Lu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: state of Lu Context triple: [Zilu, birthPlace, state of Lu]
-
A.
State of Lu
chosen
The State of Lu was an influential ancient Chinese feudal state during the Zhou dynasty, best known as the home state of Confucius and a center of early Confucian thought.
-
B.
Soso state
Soso state was a medieval West African kingdom that emerged from the decline of the Ghana Empire and later became part of the Mali Empire.
-
C.
Koti State
Koti State was a small princely state in the Simla Hills region of British India, ruled by local chiefs under British suzerainty.
-
D.
Jaora State
Jaora State was a princely state in British India, located in what is now Madhya Pradesh and ruled by a Muslim dynasty under British suzerainty.
-
E.
Mewar State
Mewar State was a historic princely state in present-day Rajasthan, India, centered on the city of Udaipur and ruled for centuries by the Sisodia Rajput dynasty.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4b6587c8190aee63dc7cff244ea |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a7a228948190b47a3a61f239e00d |
completed | April 20, 2026, 10:24 p.m. |
Created at: April 16, 2026, 11:39 a.m.