Triple
T3157952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dux Infinitos |
E66032
|
entity |
| Predicate | hasMatchFormat |
P46686
|
FINISHED |
| Object | best-of series |
—
|
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: best-of series | Statement: [Dux Infinitos, hasMatchFormat, best-of series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMatchFormat Context triple: [Dux Infinitos, hasMatchFormat, best-of series]
-
A.
hasFileFormat
Indicates that one entity (typically a digital file or resource) is encoded, stored, or represented using a specific file format defined by the other entity.
-
B.
hasFormatElement
Indicates that one entity includes, is composed of, or is associated with a specific structural or formatting component of its overall format.
-
C.
meetsFormat
Indicates that something conforms to, satisfies, or is compliant with a specified format or structural standard.
-
D.
singleMatchFormatIntroduced
Indicates that a particular single-match competition format was introduced or first implemented.
-
E.
hasPattern
Indicates that one entity exhibits, follows, or is characterized by a specific recurring form, structure, or design defined by 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_69ad85850c1481908a9e9c6242238de2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada5ec0da88190a83f3448ac76e98e |
completed | March 8, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfbf0348190952a6bca8fc5fed1 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada1e4f7288190a80a1672e458132d |
completed | March 8, 2026, 4:20 p.m. |
Created at: March 8, 2026, 3:05 p.m.