Triple
T10736271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alfonsine Tables |
E253202
|
entity |
| Predicate | widelyUsedUntil |
P6544
|
FINISHED |
| Object | 16th 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: 16th century | Statement: [Alfonsine Tables, widelyUsedUntil, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: widelyUsedUntil Context triple: [Alfonsine Tables, widelyUsedUntil, 16th century]
-
A.
usedUntil
chosen
Indicates that something remained in use or operation up to a specified time or event, after which it was no longer used.
-
B.
existedUntil
Indicates that an entity continued to exist up to, but not necessarily beyond, a specified time or event.
-
C.
widelyUsedIn
Indicates that something is commonly or extensively utilized within a particular context, domain, or group.
-
D.
firstWidelyUsedDuring
Indicates that something (such as a concept, technology, or practice) came into its first period of broad or widespread use during a specified time or era.
-
E.
areUsedSince
Indicates that entities have been in use continuously starting from a specified point in time.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d71022aee0819091a5790d3dee6777 |
completed | April 9, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69d6f309a44881908e49e3ba478c35b4 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:14 p.m.