Triple
T9356035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Biathlon |
E225141
|
entity |
| Predicate | isUnofficialTitle |
P13450
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [King of Biathlon, isUnofficialTitle, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUnofficialTitle Context triple: [King of Biathlon, isUnofficialTitle, yes]
-
A.
notOfficialNameOf
chosen
Indicates that a given name or label is used for an entity but is not its official or formally recognized name.
-
B.
isUnofficiallyRegardedAs
Indicates that something or someone is commonly or informally considered to have a certain role, status, or identity, without any official recognition or formal designation.
-
C.
isIndividualTitle
Indicates that a given title refers to a single, specific individual rather than a group, organization, or collective entity.
-
D.
notOfficialIn
Indicates that an entity does not hold an official role, status, or position within a specified organization, group, or jurisdiction.
-
E.
originallyTitleOf
Indicates that one title is the original title from which another work, edition, or localized title is derived.
- 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_69ca842abfd48190949d71c3b86eeba8 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd4fee9d4c8190a7d121c9487ccca2 |
completed | April 1, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69cc7a68ab9481909f97cb70764697cc |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:42 p.m.