Triple
T26505874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agitos |
E669541
|
entity |
| Predicate | representsValueSet |
P159490
|
FINISHED |
| Object | Paralympic values |
—
|
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: Paralympic values | Statement: [Agitos, representsValueSet, Paralympic values]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsValueSet Context triple: [Agitos, representsValueSet, Paralympic values]
-
A.
embodiesValue
chosen
Indicates that an entity exemplifies, represents, or gives concrete form to a particular value, principle, or ideal.
-
B.
representsUnionOf
Indicates that one entity is defined as the union (combined set) of several other entities.
-
C.
representsAs
Indicates that one entity serves as a depiction, symbol, or stand-in for another entity in some representational context.
-
D.
isValuedFor
Indicates that one entity is appreciated, esteemed, or considered important because of a particular quality, contribution, or characteristic it provides to another entity.
-
E.
representsInQualifiers
Indicates that an entity serves as a representative or proxy for another entity specifically within the context of qualifier information attached to a statement or relationship.
- 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 27, 2026, 1:16 a.m.