Triple
T29679047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nobatae |
E750900
|
entity |
| Predicate | receivedSubsidiesFrom |
P1704
|
FINISHED |
| Object | Byzantine Empire |
—
|
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: Byzantine Empire | Statement: [Nobatae, receivedSubsidiesFrom, Byzantine Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivedSubsidiesFrom Context triple: [Nobatae, receivedSubsidiesFrom, Byzantine Empire]
-
A.
receivedSupportFrom
chosen
Indicates that one entity obtained help, resources, or backing from another entity.
-
B.
blockRewardSpendable
Indicates that a blockchain block’s reward has matured and can now be spent or used in transactions.
-
C.
spentFuelDestination
Indicates where spent fuel is sent or stored after it has been used.
-
D.
rewardFulfilledFor
Indicates that a previously promised or expected reward has been delivered or satisfied for a particular entity.
-
E.
receivedSettlementFrom
Indicates that one party obtained a settlement payment or compensation from another party, typically as the result of a dispute, claim, or legal action.
- 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_69f0d624d7b08190ba237d226f78d0d9 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 28, 2026, 7:09 p.m.