Triple
T29905802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Villa de San Felipe de Austria |
E759530
|
entity |
| Predicate | usedAsNameInCentury |
P66067
|
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: [Villa de San Felipe de Austria, usedAsNameInCentury, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsNameInCentury Context triple: [Villa de San Felipe de Austria, usedAsNameInCentury, 17th century]
-
A.
usedAsFirstNameSinceCentury
Indicates that an entity has been used as a first name starting from a specified century.
-
B.
usedAsTownNameInCentury
chosen
Indicates that a particular name was in use as the name of a town during a specified century.
-
C.
usedInCentury
Indicates that something (such as an object, practice, or concept) was in use during a specified century.
-
D.
namedAfterCentury
Indicates that something is named after a specific century, typically reflecting that century’s time period or characteristics.
-
E.
associatedWithCenturyOfNameBearer
Indicates that an entity is linked to the historical century in which the person (name bearer) associated with it lived or is primarily known.
- 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_69f224600590819085e148a01c056ef6 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: April 29, 2026, 6:08 p.m.