Triple
T31858352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lordship of Negroponte |
E813255
|
entity |
| Predicate | overlordType |
P155300
|
FINISHED |
| Object | suzerainty |
—
|
LITERAL FINISHED |
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: suzerainty | Statement: [Lordship of Negroponte, overlordType, suzerainty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overlordType Context triple: [Lordship of Negroponte, overlordType, suzerainty]
-
A.
typeOfOverlordship
chosen
Indicates a hierarchical relationship in which one entity holds overlordship, or superior controlling authority, over another.
-
B.
overlordDuringReign
Indicates that one entity served as the ruling overlord of another entity during a specified reign period.
-
C.
lordOf
Indicates that one entity holds lordship, authority, or dominion over another entity.
-
D.
titleOfOverlord
Indicates that one entity is the formal title or designation held by an overlord (a ruling or dominant authority) in relation to another entity.
-
E.
relationshipToOverlords
Indicates the nature or type of connection, role, or allegiance that an entity has in relation to its overlords.
- 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_69f348ebf32881908d9439646933dc76 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b06b872481908372becd54a1792e |
completed | May 3, 2026, 2:18 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:52 p.m.