Triple
T35814368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purchase of Cyprus from Richard I of England |
E1035314
|
entity |
| Predicate | hasNewOwner |
P12936
|
FINISHED |
| Object | Guy of Lusignan |
—
|
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: Guy of Lusignan | Statement: [Purchase of Cyprus from Richard I of England, hasNewOwner, Guy of Lusignan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNewOwner Context triple: [Purchase of Cyprus from Richard I of England, hasNewOwner, Guy of Lusignan]
-
A.
ownershipChangedAfter
Indicates that the ownership of an entity became different at some point after a specified time or event.
-
B.
hasOwnerInThePast
Indicates that an entity was owned by another entity at some time in the past, but not necessarily in the present.
-
C.
hasPlannedOwner
Indicates that an entity is intended or scheduled to become the owner of another entity in the future.
-
D.
ownershipTransferredTo
chosen
Indicates that the legal or formal ownership of an entity has been transferred from one party to another specified party.
-
E.
hasOwnerWhoLaterOwned
Indicates that an entity is owned by someone who, at a later time, also became the owner of another specified entity.
- 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_6a00315632a8819092290f455babd7ee |
completed | May 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_6a002f54a0dc81909b0e54c5e110e67c |
completed | May 10, 2026, 7:10 a.m. |
Created at: May 3, 2026, 4:06 p.m.