Triple
T28864817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Strid |
E728968
|
entity |
| Predicate | hasWarningSigns |
P5961
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [The Strid, hasWarningSigns, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWarningSigns Context triple: [The Strid, hasWarningSigns, yes]
-
A.
warningSigns
Indicates that one entity presents or serves as cautionary indications or alerts about potential danger, problems, or undesirable outcomes related to another entity.
-
B.
hasHazardSignage
chosen
Indicates that appropriate warning or hazard signs are present to alert people to potential dangers associated with the entity.
-
C.
hasSign
Indicates that an entity possesses, displays, or is associated with a particular sign or symbol.
-
D.
hasSignificant
Indicates that one entity possesses or exhibits a level of importance, impact, or relevance that is notably large or meaningful in relation to another entity or context.
-
E.
showsSignOf
Indicates that one entity exhibits evidence, symptoms, or characteristics suggesting the presence or occurrence of another entity, condition, or state.
- 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 28, 2026, 6:48 a.m.