Triple
T6864693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glico Running Man |
E158367
|
entity |
| Predicate | currentVersionInstalled |
P13927
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Glico Running Man, currentVersionInstalled, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentVersionInstalled Context triple: [Glico Running Man, currentVersionInstalled, 2014]
-
A.
currentVersionDefinedIn
Indicates that the current or active version of an entity is specified or established within a particular source, document, or context.
-
B.
currentVersionAdopted
chosen
Indicates that a specified version is the one presently in use or officially adopted by the relevant entity or system.
-
C.
currentCoreVersionEnactedIn
Indicates that a specific version of the core (e.g., a standard, framework, or core specification) is currently in force within a given context, jurisdiction, or system.
-
D.
latestVersion
Indicates that one entity is the most recent or up-to-date version of another entity within a sequence or set of versions.
-
E.
exportVersion
Indicates the specific release or revision identifier of an item as it is prepared for or used in export.
- 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_69c68830cdbc8190a8301c7a9d9f651a |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6da3ce95081909a424ac04bc7fa07 |
completed | March 27, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b168908190b2f7c724b1bc7fc9 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:21 p.m.