Triple
T32348579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Guard |
E826531
|
entity |
| Predicate | timeOfGreatestStrength |
P78121
|
FINISHED |
| Object | reign of Moulay Ismail |
—
|
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: reign of Moulay Ismail | Statement: [Black Guard, timeOfGreatestStrength, reign of Moulay Ismail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfGreatestStrength Context triple: [Black Guard, timeOfGreatestStrength, reign of Moulay Ismail]
-
A.
strengthPeak
Indicates the point or period at which an entity’s strength reaches its maximum level.
-
B.
strongestIn
Indicates that one entity possesses the greatest strength or power within a specified group, context, or comparison set.
-
C.
observationBestTime
Indicates that there is an identified optimal or most suitable time period during which the observation of something should be made.
-
D.
strongestPeriodUnder
chosen
Indicates that one entity represents the time period during which another entity exhibits its maximum or strongest value, effect, or performance.
-
E.
strongerAt
Indicates that one entity has greater strength, power, or effectiveness than another in a specified context, condition, or domain.
- 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_69f34914dfc48190a390cd0720d9e86f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 1, 2026, 12:49 a.m.