Triple
T26066661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Passfield |
E657420
|
entity |
| Predicate | hasOrderInPrecedence |
P163675
|
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: [Baron Passfield, hasOrderInPrecedence, baron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrderInPrecedence Context triple: [Baron Passfield, hasOrderInPrecedence, baron]
-
A.
belongsToOrderOfPrecedence
chosen
Indicates that one entity is assigned a specific position or rank within an established order of precedence relative to other entities.
-
B.
confersPrecedenceIn
Indicates that one entity is granted higher priority, rank, or standing over another within a specified context or domain.
-
C.
hasPrecedence
Indicates that one entity occurs, is considered, or is applied before another in order, priority, or importance.
-
D.
isOrderOf
Indicates that one entity specifies the sequence, arrangement, or ranking in which elements of another entity are organized or occur.
-
E.
precedesInStability
Indicates that one entity is more stable than another, coming earlier in an ordering based on stability.
- 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 26, 2026, 7:24 p.m.