Triple
T28880726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GW170814 |
E732408
|
entity |
| Predicate | hasEventNameConvention |
P55768
|
FINISHED |
| Object | date-based YYMMDD format |
—
|
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: date-based YYMMDD format | Statement: [GW170814, hasEventNameConvention, date-based YYMMDD format]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEventNameConvention Context triple: [GW170814, hasEventNameConvention, date-based YYMMDD format]
-
A.
hasNameInEvent
Indicates that an entity is associated with a specific name or label within the context of a particular event.
-
B.
hasRuleName
Indicates that an entity is associated with a specific rule identified by a particular name.
-
C.
namespaceConvention
Indicates the naming and structural rules that govern how namespaces are defined, organized, and referenced in a system.
-
D.
namingConventionType
chosen
Indicates the specific style or set of rules used for naming entities or elements in a given context.
-
E.
hasProperName
Indicates that an entity is associated with a specific proper name used to uniquely identify it.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65a6d639481909e661755a5838a47 |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 7:43 a.m.