Triple
T12469025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Welsh 3000s |
E298003
|
entity |
| Predicate | disputedPeakCount |
P79279
|
FINISHED |
| Object | 14 |
—
|
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: 14 | Statement: [Welsh 3000s, disputedPeakCount, 14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disputedPeakCount Context triple: [Welsh 3000s, disputedPeakCount, 14]
-
A.
countIsDisputed
chosen
Indicates that the reported numerical value (such as a count, total, or tally) is contested or not agreed upon by relevant parties.
-
B.
numberOfDisputations
Indicates the quantity of disputations (formal debates or arguments) associated with an entity.
-
C.
disputed
Indicates that there is active disagreement or contestation over the validity, ownership, interpretation, or status of the relationship or claim between the entities.
-
D.
contestedFrequency
Indicates that the frequency or rate of an event, action, or occurrence is disputed or not agreed upon between parties.
-
E.
statusDisputedBy
Indicates that the validity, accuracy, or recognition of a status is being challenged or contested by a specified party.
- 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_69d6ada270808190b1a2b2e7b02bb426 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e626dbc8190ac7dcdb542ba9b0c |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d3f701c81909dd0e00251ac8553 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:56 p.m.