Triple
T6254729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birka and Hovgården |
E140133
|
entity |
| Predicate | criteriaForSelection |
P136
|
FINISHED |
| Object | criterion (iii) |
—
|
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: criterion (iii) | Statement: [Birka and Hovgården, criteriaForSelection, criterion (iii)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: criteriaForSelection Context triple: [Birka and Hovgården, criteriaForSelection, criterion (iii)]
-
A.
selectionCriteria
chosen
Indicates the conditions or rules used to choose certain entities from a larger set.
-
B.
evaluationCriteriaInclude
Indicates that certain criteria are part of, or explicitly included in, the set of standards used to evaluate something.
-
C.
listingCriterion
Indicates the rule or standard used to determine how items are selected, ordered, or displayed in a listing.
-
D.
selectionCharacteristic
Indicates a distinguishing feature or criterion used to choose or differentiate one entity from others.
-
E.
selectionReason
Indicates the reason or justification for choosing or selecting one entity over alternatives.
- 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_69c008b4858c819095b0199114a9a87b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06363d6008190bf05e003b1f74497 |
completed | March 22, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69c05605566c81908e197f5accd072d2 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:24 p.m.