Triple
T35814359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purchase of Cyprus from Richard I of England |
E1035314
|
entity |
| Predicate | hasSeller |
P7792
|
FINISHED |
| Object | Richard I of England |
—
|
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: Richard I of England | Statement: [Purchase of Cyprus from Richard I of England, hasSeller, Richard I of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeller Context triple: [Purchase of Cyprus from Richard I of England, hasSeller, Richard I of England]
-
A.
seller
chosen
Indicates a relationship where one entity offers or provides goods, services, or assets to another in exchange for payment or other compensation.
-
B.
wantsToSell
Indicates that one entity has the intention or desire to sell another entity.
-
C.
soldFrom
Indicates that something was transferred in a sale originating from a particular source, such as a seller, location, or organization.
-
D.
sellerType
Indicates the classification or category of the party acting as the seller in a transaction or relationship.
-
E.
alsoSoldBy
Indicates that the same item or product is offered for sale by an additional seller or vendor beyond the primary one.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a002ae74da08190a4b47e0ff0f7f8fe |
completed | May 10, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_6a0029cc369c81909578e52c4a75ab18 |
completed | May 10, 2026, 6:46 a.m. |
Created at: May 3, 2026, 4:06 p.m.