Triple
T1429023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jethou |
E30400
|
entity |
| Predicate | leaseholder |
P10974
|
FINISHED |
| Object | private individual |
—
|
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: private individual | Statement: [Jethou, leaseholder, private individual]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leaseholder Context triple: [Jethou, leaseholder, private individual]
-
A.
leaseRecipient
chosen
Indicates the party that receives or holds rights to use a property or asset under a lease agreement from another party.
-
B.
alsoTenant
Indicates that two or more entities share the status of being tenants, typically occupying the same property or rental arrangement.
-
C.
anchorTenant
Indicates that an entity serves as a primary or major tenant whose presence helps attract other tenants or users to a shared space or platform.
-
D.
leagueOfTenant
Indicates that a tenant is a member of, or participates in, a particular league or organized competition.
-
E.
holder
Indicates that one entity possesses, controls, or has custody of another entity, typically in a temporary or contextual sense.
- 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_69a498fc69ec8190b61722bd4b67c4d2 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c500a9888190a16fbb1ec97a79c9 |
completed | March 1, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69a4c4771c9481908ae47c959debbe77 |
completed | March 1, 2026, 10:57 p.m. |
Created at: March 1, 2026, 8 p.m.