Triple
T2935089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacArthur Park Lake |
E79245
|
entity |
| Predicate | hasSurroundingLandUse |
P43475
|
FINISHED |
| Object | high‑density residential |
—
|
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: high‑density residential | Statement: [MacArthur Park Lake, hasSurroundingLandUse, high‑density residential]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurroundingLandUse Context triple: [MacArthur Park Lake, hasSurroundingLandUse, high‑density residential]
-
A.
hasNearbyLandUse
Indicates that one land area is located close to another area characterized by a specific type of land use.
-
B.
hasLandUseCharacter
chosen
Indicates that one entity possesses or is associated with a particular type or pattern of land use.
-
C.
landUseIncludes
Indicates that a specified land area contains or permits the specified type(s) of land use within its boundaries.
-
D.
hasSurroundings
Indicates that an entity is located within or encircled by a particular environment, context, or set of surrounding elements.
-
E.
otherLandUse
Indicates that the land is used for purposes that do not fall into any of the primary or predefined land-use categories.
- 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_69ad8b0fbab081908f6a61567c045d8d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad983c84688190aa7ed5b8091fb140 |
completed | March 8, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69ad96088fb481909976b436c2b729d9 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:56 p.m.