Triple
T23766000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philip Henslowe |
E587378
|
entity |
| Predicate | leasedLandFor |
P153875
|
FINISHED |
| Object | Rose Theatre |
—
|
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: Rose Theatre | Statement: [Philip Henslowe, leasedLandFor, Rose Theatre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leasedLandFor Context triple: [Philip Henslowe, leasedLandFor, Rose Theatre]
-
A.
soldLandFor
Indicates that one party transferred ownership of land to another party in exchange for payment or other agreed compensation.
-
B.
ownsLandFor
Indicates that one entity possesses or holds ownership rights to land for the benefit, use, or purpose of another entity.
-
C.
promiseOfLandTo
Indicates that one entity has made a commitment or assurance to grant or transfer land to another entity.
-
D.
cededLandFor
Indicates that one party transferred control or ownership of land to another party, typically as part of an agreement, treaty, or settlement.
-
E.
ownedLandBy
Indicates that one entity possesses legal or recognized ownership rights over a piece or area of land associated with another entity.
- F. None of above. chosen
Provenance (4 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_69e2490b8ac48190a6b35f1d5500486b |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bdb5b0408190b46661d80e37b509 |
completed | April 29, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_69f15ed138f88190a8ae555422978908 |
completed | April 29, 2026, 1:28 a.m. |
Created at: April 17, 2026, 7:15 p.m.