Triple
T9670245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byzantine military aristocracy |
E234005
|
entity |
| Predicate | declinesAfter |
P19208
|
FINISHED |
| Object | 11th century |
—
|
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: 11th century | Statement: [Byzantine military aristocracy, declinesAfter, 11th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declinesAfter Context triple: [Byzantine military aristocracy, declinesAfter, 11th century]
-
A.
declineAfter
chosen
Indicates that one entity or value decreases or worsens following another specified event, condition, or point in time.
-
B.
declinedAround
Indicates that something decreased in value, intensity, or quantity in the time period surrounding a specified point or event.
-
C.
endedOrDeclinedAfter
Indicates that one entity’s involvement, status, or offer concluded or was rejected following the occurrence or completion of another specified event or condition.
-
D.
declinedDuring
Indicates that one entity’s value, condition, or status decreased over the course of a specified time period or event.
-
E.
declineBeganInPeriod
Indicates that the onset of a decline in the subject occurred during the specified time period.
- 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_69ca848f55e48190b3f67252571c3d45 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c3ec17081908c2da74a1d1f49da |
completed | April 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b3239c8190b3ae3b9bd121e4bd |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:15 p.m.