Triple
T5111602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ravenclaw |
E115224
|
entity |
| Predicate | sortingCriteria |
P48210
|
FINISHED |
| Object | high intelligence |
—
|
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: high intelligence | Statement: [Ravenclaw, sortingCriteria, high intelligence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sortingCriteria Context triple: [Ravenclaw, sortingCriteria, high intelligence]
-
A.
selectionCriteria
Indicates the conditions or rules used to choose certain entities from a larger set.
-
B.
listingCriterion
chosen
Indicates the rule or standard used to determine how items are selected, ordered, or displayed in a listing.
-
C.
selectionOrderAdjustment
Indicates a modification to the original order in which items or options were selected, such as reordering or adjusting their selection sequence.
-
D.
orderedBy
Indicates that one entity has placed a request or purchase for another entity, typically specifying who initiated the order.
-
E.
selectionOrderInfluencedBy
Indicates that the order in which items are selected is affected or determined by another factor, condition, or entity.
- 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_69bd4441d1648190a54a533895041987 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75ca57e881908242def2a032902e |
completed | March 20, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69bd715fe3a8819087d3065adddba515 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:41 p.m.