Triple
T24902829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California Products Corporation |
E623624
|
entity |
| Predicate | surfaceApplication |
P157786
|
FINISHED |
| Object | outdoor sports courts |
—
|
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: outdoor sports courts | Statement: [California Products Corporation, surfaceApplication, outdoor sports courts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceApplication Context triple: [California Products Corporation, surfaceApplication, outdoor sports courts]
-
A.
applicationTool
Indicates that one entity is a tool or instrument used to apply, operate, or carry out the function of another entity.
-
B.
surfaceAccess
Indicates that one entity provides a means for another entity to reach, enter, or interact with a surface or outer layer.
-
C.
aplicación
Indicates that one entity is the use or implementation of another entity for a specific purpose or function.
-
D.
applicationInterface
Indicates that one entity serves as an interface or interaction layer through which another entity accesses or uses an application’s functionality.
-
E.
exampleApplication
Indicates that something serves as a representative or illustrative instance of how an application is used or functions.
- 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_69e2fac797cc8190b30d77f4121099ac |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
| PDg | Predicate description generation | batch_69f44a3adb7c8190941572f718b3b93c |
completed | May 1, 2026, 6:37 a.m. |
Created at: April 18, 2026, 5:27 a.m.