Triple
T15867633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Necessary Existent |
E384752
|
entity |
| Predicate | groundsExistenceOf |
P120828
|
FINISHED |
| Object | all other existents |
—
|
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: all other existents | Statement: [Necessary Existent, groundsExistenceOf, all other existents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groundsExistenceOf Context triple: [Necessary Existent, groundsExistenceOf, all other existents]
-
A.
coversGrounds
Indicates that one entity extends over, occupies, or lies across the surface area of another entity (typically land or grounds).
-
B.
existedUnder
Indicates that one entity existed within the authority, jurisdiction, or domain of another entity during a certain period.
-
C.
existsWithin
Indicates that one entity is located inside the spatial, temporal, or conceptual boundaries of another entity.
-
D.
hasGrounds
Indicates that one entity possesses or includes a physical area of land or outdoor space associated with it.
-
E.
isGreenSpaceFor
Indicates that one entity serves as a designated green or open space intended for use or benefit by another entity.
- 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142b976c081908d3ba3e705419f3a |
completed | April 16, 2026, 8:12 p.m. |
| PDg | Predicate description generation | batch_69e174da2c2c819099ec46616798245a |
completed | April 16, 2026, 11:46 p.m. |
Created at: April 10, 2026, 4:50 a.m.