Triple
T5619178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AstroTurf |
E147555
|
entity |
| Predicate | hasGenericUseAs |
P23148
|
FINISHED |
| Object | generic term for artificial turf in popular usage |
—
|
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: generic term for artificial turf in popular usage | Statement: [AstroTurf, hasGenericUseAs, generic term for artificial turf in popular usage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGenericUseAs Context triple: [AstroTurf, hasGenericUseAs, generic term for artificial turf in popular usage]
-
A.
hasGeneralPurpose
Indicates that one entity serves as the broad, overarching function, role, or intended use of another entity.
-
B.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
C.
isUsedUnder
Indicates that one entity is utilized or applied within the context, conditions, or framework defined by another entity.
-
D.
hasHumanUse
Indicates that something is used, employed, or utilized by humans for a particular purpose or benefit.
-
E.
hasGenericName
chosen
Indicates that an entity is associated with a non-brand, generic name that designates its general type or class.
- 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_69c00905d4588190bd967842bbcf2219 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c021dd5d0081909d18d16596fac507 |
completed | March 22, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69c01b1d4b108190846ce586dc783acf |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:40 p.m.