Triple
T8275067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Action Green |
E193524
|
entity |
| Predicate | typicalUsageArea |
P21833
|
FINISHED |
| Object | jerseys |
—
|
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: jerseys | Statement: [Action Green, typicalUsageArea, jerseys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalUsageArea Context triple: [Action Green, typicalUsageArea, jerseys]
-
A.
typicalSectorUse
Indicates the type of sector in which something is most commonly or characteristically used.
-
B.
hasTypicalUsageRegion
Indicates that something is most commonly or characteristically used within a particular geographic region.
-
C.
typicalUseLocation
chosen
Indicates the usual or most common location where an entity is used or operates.
-
D.
usageType
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
-
E.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
- 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_69ca82e14ae481908ffdb822cd2192bc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb798bc29c8190927ef4b0662d6b98 |
completed | March 31, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69cb70a4525481909399d313a6247ace |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:51 p.m.