Triple
T33109841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Francisco street grid |
E847299
|
entity |
| Predicate | doesNotFullyCoverArea |
P10124
|
FINISHED |
| Object | Golden Gate Park |
—
|
NE NERFINISHED |
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: Golden Gate Park | Statement: [San Francisco street grid, doesNotFullyCoverArea, Golden Gate Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotFullyCoverArea Context triple: [San Francisco street grid, doesNotFullyCoverArea, Golden Gate Park]
-
A.
doesNotCover
chosen
Indicates that one entity fails to include, protect, or extend over another entity or area.
-
B.
mayCoverArea
Indicates that one entity is permitted or able to extend over, include, or encompass a specified spatial area.
-
C.
coversAreaOutside
Indicates that one entity extends over or encompasses a region that lies beyond the boundaries of another specified area.
-
D.
partlyCoveredBy
Indicates that one entity is covered or overlapped by another entity, but only to a partial extent rather than completely.
-
E.
partiallyOn
Indicates that one entity rests or extends over another such that only a portion of its area, volume, or length is supported or in contact.
- 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_69f3495686508190b76bf20fa5e00bf7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:27 a.m.