Triple
T28080590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green |
E709663
|
entity |
| Predicate | isSymbolicallyAssociatedWith |
P89328
|
FINISHED |
| Object | safety |
—
|
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: safety | Statement: [Green, isSymbolicallyAssociatedWith, safety]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSymbolicallyAssociatedWith Context triple: [Green, isSymbolicallyAssociatedWith, safety]
-
A.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
B.
isRelatedSymbol
Indicates that one symbol has a defined relationship or association with another symbol, such as similarity, correspondence, or functional connection.
-
C.
symbolicRelation
Indicates a relationship where one entity stands for, represents, or conveys meaning about another through symbols or abstract signs.
-
D.
associatedWithAssociation
Indicates a relationship where an entity is linked or connected to a particular association or organization.
-
E.
symbolizedIn
chosen
Indicates that one entity serves as a symbol or representation of another entity.
- 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_69ef9b7037f0819095bb90eaccbcaf32 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 8:51 p.m.