Triple
T20149242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baiju Noyan |
E491388
|
entity |
| Predicate | approximateEndOfActivity |
P8204
|
FINISHED |
| Object | 1250s |
—
|
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: 1250s | Statement: [Baiju Noyan, approximateEndOfActivity, 1250s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateEndOfActivity Context triple: [Baiju Noyan, approximateEndOfActivity, 1250s]
-
A.
endOfActivity
Indicates that a particular activity has reached its completion or final point in time.
-
B.
timePeriodEndApprox
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
C.
typicallyEndsAt
Indicates that an event, process, or activity most commonly or usually concludes at a particular time, place, or state.
-
D.
officeEndApproximate
Indicates that an office or term ended around an approximate date rather than on a precisely known day.
-
E.
hasApproximateEnd
chosen
Indicates that an entity’s end point, time, or boundary is known only approximately rather than precisely.
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e667a0c0e881909a4f21a5d22973d2 |
completed | April 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69e54cfd924881909b55f3e4d3e7e070 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:33 p.m.