Triple
T31929827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint of the Flying |
E815211
|
entity |
| Predicate | hasSubjectCentury |
P168452
|
FINISHED |
| Object | 17th 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: 17th century | Statement: [Saint of the Flying, hasSubjectCentury, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubjectCentury Context triple: [Saint of the Flying, hasSubjectCentury, 17th century]
-
A.
claimedInCentury
Indicates that a claim or assertion was made or recorded during a specified century.
-
B.
isFromCentury
chosen
Indicates that an entity originates from, belongs to, or is associated with a specified century.
-
C.
endedInCentury
Indicates that an event, period, or process concluded during a specified century.
-
D.
associatedWithCentury
Indicates that something has a relevant connection or linkage to a particular century, such as occurring in, belonging to, or being characteristic of that time period.
-
E.
ownedInCentury
Indicates that one entity owned another during a specified century.
- 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_69f348f3035c81908558e2339955abb3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fed6da0390819096b88ef4714b144e |
completed | May 9, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69fed53517d081909966f31707625f1a |
completed | May 9, 2026, 6:33 a.m. |
Created at: May 1, 2026, 12:04 a.m.