Triple
T30462604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parthian nobility |
E775051
|
entity |
| Predicate | couldChallenge |
P15175
|
FINISHED |
| Object | royal authority |
—
|
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: royal authority | Statement: [Parthian nobility, couldChallenge, royal authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: couldChallenge Context triple: [Parthian nobility, couldChallenge, royal authority]
-
A.
challengeTo
Indicates that one entity issues a challenge or dare for another entity to face or respond to.
-
B.
mayBeChallengedBy
chosen
Indicates that one entity is allowed or able to be opposed, questioned, or contested by another entity.
-
C.
challengeUndertaken
Indicates that an entity has accepted and is actively engaging in a specific challenge or demanding task.
-
D.
canBeChallengedOn
Indicates that one entity’s claim, decision, or status is open to being questioned, disputed, or formally contested by another entity.
-
E.
challengeType
Indicates the specific category or kind of challenge associated with an action or relationship between entities.
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:10 p.m.