Triple
T36110069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Loam |
E1044468
|
entity |
| Predicate | authorityChallengedBy |
P192848
|
FINISHED |
| Object | Crichton |
—
|
NE NERFINISHED |
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: Crichton | Statement: [Lord Loam, authorityChallengedBy, Crichton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorityChallengedBy Context triple: [Lord Loam, authorityChallengedBy, Crichton]
-
A.
authorityQuestionedBy
chosen
Indicates that the legitimacy, power, or control of one entity is challenged or disputed by another entity.
-
B.
authorityWithin
Indicates that one entity holds recognized power, control, or decision-making authority inside the scope, domain, or jurisdiction defined by another entity.
-
C.
deniedAuthorityOf
Indicates that one entity refused to recognize, accept, or submit to the authority, power, or legitimacy of another entity.
-
D.
authorityBasedOn
Indicates that one entity’s authority or power is derived from, justified by, or contingent upon another specified basis or source.
-
E.
authorityGranted
Indicates that one entity has formally given another entity the power, rights, or permission to act or make decisions, typically within a defined scope or context.
- 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_69f76e344a4c8190af3858c6d78ba88f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe38be079c8190a240191ac0e73e3a |
completed | May 8, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69fe350344508190930de2218156ca02 |
completed | May 8, 2026, 7:09 p.m. |
Created at: May 3, 2026, 4:08 p.m.