Triple
T11719704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuser family |
E278593
|
entity |
| Predicate | familyEstateCurrentUse |
P14072
|
FINISHED |
| Object | public park |
—
|
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: public park | Statement: [Kuser family, familyEstateCurrentUse, public park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyEstateCurrentUse Context triple: [Kuser family, familyEstateCurrentUse, public park]
-
A.
houseUse
Indicates how a house or dwelling is used or purposed (e.g., residential, commercial, mixed-use).
-
B.
heirOfEstate
Indicates that one entity is legally designated to inherit the estate or property of another entity, typically upon that entity’s death.
-
C.
landUseIncludes
Indicates that a specified land area contains or permits the specified type(s) of land use within its boundaries.
-
D.
residenceUsedFor
Indicates that a particular residence is used for a specific purpose, function, or activity.
-
E.
primaryLandUse
chosen
Indicates the main or dominant way in which a given piece of land is utilized or designated (e.g., residential, agricultural, commercial).
- 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4c26e4c8190ae30d906b4fd4221 |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7d483081909c2a101087515d74 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.