Triple
T27789159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ciudad de la Plata de la Nueva Toledo |
E701035
|
entity |
| Predicate | usedAsNameInPeriod |
P145623
|
FINISHED |
| Object | colonial era |
—
|
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: colonial era | Statement: [Ciudad de la Plata de la Nueva Toledo, usedAsNameInPeriod, colonial era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsNameInPeriod Context triple: [Ciudad de la Plata de la Nueva Toledo, usedAsNameInPeriod, colonial era]
-
A.
usesNameSince
Indicates that an entity has been using a particular name continuously starting from a specified point in time.
-
B.
usedAsReportingNameDuring
Indicates that one entity functioned as the reporting name or callsign for another entity during a specified time period.
-
C.
historicalNameUsedIn
chosen
Indicates that a historical or former name was used to refer to a particular entity in some context.
-
D.
usedEraName
Indicates that an entity employed or referenced a specific historical or calendrical era name in its dating or designation.
-
E.
usedNameToYear
Indicates that a particular name was in use or valid during a specified year.
- 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_69ef6a50d8088190acbf3dfbb06d8091 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 27, 2026, 5:26 p.m.