Triple
T18917149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sergeants' Revolt |
E462750
|
entity |
| Predicate | primaryLeaderRank |
P105228
|
FINISHED |
| Object | sergeant |
—
|
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: sergeant | Statement: [Sergeants' Revolt, primaryLeaderRank, sergeant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryLeaderRank Context triple: [Sergeants' Revolt, primaryLeaderRank, sergeant]
-
A.
ledByRank
chosen
Indicates that the leadership of an entity is determined or characterized by a specific rank or hierarchical position.
-
B.
initialLeader
Indicates that an entity serves as the first or original leader of another entity, typically at the start of its existence or a defined period.
-
C.
targetLeader
Indicates that one entity is the primary leader, focal authority, or main decision-maker targeted or referenced by another entity or action.
-
D.
leaderSince
Indicates that an entity has held a leadership role over another entity starting from a specified point in time.
-
E.
pointsLeader
Indicates that the subject entity is the current leader in points relative to other entities in a given context or competition.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c627724881909cf63c67d64321e8 |
completed | April 20, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.