Triple
T14774803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Ralph |
E347229
|
entity |
| Predicate | hasSurfaceHistory |
P87141
|
FINISHED |
| Object | artificial turf |
—
|
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: artificial turf | Statement: [The Ralph, hasSurfaceHistory, artificial turf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurfaceHistory Context triple: [The Ralph, hasSurfaceHistory, artificial turf]
-
A.
hasHistoryIn
Indicates that an entity has a past involvement, presence, or record of activity within a particular domain, context, or location.
-
B.
hasResourceHistory
chosen
Indicates that an entity is associated with a record or sequence of past states, usages, or changes of a particular resource over time.
-
C.
hasTypeHistory
Indicates that an entity is associated with a record or sequence of its past and present types or classifications over time.
-
D.
hasHistoryPeriod
Indicates that something is associated with, belongs to, or occurs within a specific historical period or era.
-
E.
hasStructureHistory
Indicates that there exists a record or account detailing the past states, changes, or development of a structure over time.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec815dd5081909e927911c06b2d66 |
completed | April 14, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.