Triple
T3751861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viscount Lascelles |
E81349
|
entity |
| Predicate | precedenceAbove |
P34031
|
FINISHED |
| Object | baron |
—
|
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: baron | Statement: [Viscount Lascelles, precedenceAbove, baron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precedenceAbove Context triple: [Viscount Lascelles, precedenceAbove, baron]
-
A.
hasLowerPrecedenceThan
Indicates that one item is ranked or ordered with a lower priority or importance compared to another item.
-
B.
hasPrecedence
chosen
Indicates that one entity occurs, is considered, or is applied before another in order, priority, or importance.
-
C.
orderPrecedence
Indicates that one entity must come before another in a defined sequence or priority order.
-
D.
confersPrecedenceIn
Indicates that one entity is granted higher priority, rank, or standing over another within a specified context or domain.
-
E.
sharesPrecedenceWith
Indicates that two entities occupy the same level in an ordering or hierarchy, such that neither has priority or precedence over the other.
- 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_69ad8b19b7b08190a6188804e99c53e9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb92135c819093f6d616d3ad28ff |
completed | March 8, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69adc04adebc819088d7f36d0ac343a6 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.