Triple
T15391902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Universal Spider |
E368064
|
entity |
| Predicate | appliedPeriod |
P302
|
FINISHED |
| Object | reign of Louis XI (1461–1483) |
—
|
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 Louis XI (1461–1483) | Statement: [the Universal Spider, appliedPeriod, reign of Louis XI (1461–1483)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedPeriod Context triple: [the Universal Spider, appliedPeriod, reign of Louis XI (1461–1483)]
-
A.
periodizedAs
Indicates that something has been divided or organized into distinct time periods according to a particular periodization scheme.
-
B.
appliedSince
Indicates that a particular condition, rule, status, or action has been in effect starting from a specified point in time and continues from that date onward.
-
C.
associatedPeriodEnd
Indicates the ending point or final date of the time period with which something is associated.
-
D.
refersToPeriod
Indicates that one entity designates, references, or is associated with a specific time period or interval.
-
E.
timePeriod
chosen
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e7838b48190862b43c6c8620692 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27b8cac8190bfa77698d53c5d1c |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.