Triple
T23300814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central London Property Trust Ltd v High Trees House Ltd |
E590296
|
entity |
| Predicate | estoppelType |
P151775
|
FINISHED |
| Object | promissory estoppel |
—
|
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: promissory estoppel | Statement: [Central London Property Trust Ltd v High Trees House Ltd, estoppelType, promissory estoppel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estoppelType Context triple: [Central London Property Trust Ltd v High Trees House Ltd, estoppelType, promissory estoppel]
-
A.
stoppedBy
Indicates that one entity causes another entity to cease moving, operating, or continuing an action.
-
B.
typicalStallType
Indicates the usual or most common type or category of stall associated with an entity.
-
C.
statutoryType
Indicates the specific legal or statutory category under which something is formally classified or regulated.
-
D.
legalStatusEnd
Indicates the point or event at which a previously valid legal status, condition, or arrangement ceases to be in effect.
-
E.
restraintType
Indicates the specific kind or method of restraint applied in a given situation or relationship.
- 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_69e25d1c0ecc8190a355aa229f06d0e0 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196d2b5dc819084b4d0290184de62 |
completed | April 29, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d88b4ec8190a2a17a88e0eda178 |
completed | April 28, 2026, 2:38 a.m. |
Created at: April 17, 2026, 5:04 p.m.