Triple
T26572224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adderley v. Florida |
E666855
|
entity |
| Predicate | propertyTypeAtIssue |
P149833
|
FINISHED |
| Object | county jail driveway and grounds |
—
|
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: county jail driveway and grounds | Statement: [Adderley v. Florida, propertyTypeAtIssue, county jail driveway and grounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propertyTypeAtIssue Context triple: [Adderley v. Florida, propertyTypeAtIssue, county jail driveway and grounds]
-
A.
propertyType_id
chosen
Indicates a relationship that specifies the type or category of a property associated with an entity.
-
B.
propertyTypeOwned
Indicates that one entity owns a specific type or category of property in relation to another entity.
-
C.
collateralType
Indicates the kind or category of collateral associated with an obligation, agreement, or financial exposure.
-
D.
propertyType_rid
Indicates that an entity is associated with a specific property type identified by a unique resource identifier (RID).
-
E.
propertyType_rtx
Indicates that one entity has a specific type or category of property in relation to another 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_69ee9cfa21c081909e4e36e087debfc6 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 1:58 a.m.