Triple
T25526630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Roodee |
E639791
|
entity |
| Predicate | hasInfieldUse |
P151016
|
FINISHED |
| Object | car parking |
—
|
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: car parking | Statement: [The Roodee, hasInfieldUse, car parking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInfieldUse Context triple: [The Roodee, hasInfieldUse, car parking]
-
A.
hasInfield
Indicates that an entity possesses or includes a designated infield area, typically within a larger spatial or structural context.
-
B.
infieldUse
chosen
Indicates that something is used or applied within a specific field, area, or domain.
-
C.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
D.
isInUse
Indicates that an entity is currently being utilized or actively engaged in its intended function or operation.
-
E.
isUsedUnder
Indicates that one entity is utilized or applied within the context, conditions, or framework defined by 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_69e75dbf3f9c8190b3f2a75d1b75d127 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 21, 2026, 3:11 p.m.