Triple
T37465725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Year of the Gryphon |
E931028
|
entity |
| Predicate | formatAffected |
P190405
|
FINISHED |
| Object | Standard |
—
|
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: Standard | Statement: [Year of the Gryphon, formatAffected, Standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formatAffected Context triple: [Year of the Gryphon, formatAffected, Standard]
-
A.
standAffected
Indicates that an entity is in a state or position of being impacted or influenced by another entity or event.
-
B.
areAffectedBy
Indicates that one entity experiences an effect, influence, or impact as a result of another entity or event.
-
C.
operatorAffected
Indicates that an operator is impacted or influenced by a particular action, event, or condition.
-
D.
doctrineAffected
Indicates that a particular doctrine, belief system, or set of principles is influenced, altered, or impacted by another entity or factor.
-
E.
affectedRecord
Indicates that one entity is a record that is impacted, modified, or otherwise influenced as a result of an action or event involving another entity.
- F. None of above. chosen
Provenance (4 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
| PDg | Predicate description generation | batch_69fcc4b5f22c8190b8b256adbdc2570c |
completed | May 7, 2026, 4:58 p.m. |
Created at: May 3, 2026, 4:17 p.m.