Triple
T19283360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paita |
E482244
|
entity |
| Predicate | timePeriodNotability |
P8452
|
FINISHED |
| Object | 19th 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: 19th century | Statement: [Paita, timePeriodNotability, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodNotability Context triple: [Paita, timePeriodNotability, 19th century]
-
A.
notableDuring
chosen
Indicates that something was especially prominent, active, or significant during a particular time period or event.
-
B.
timePeriodOfMajorImportance
Indicates that a particular time period holds significant importance or prominence within a given context or domain.
-
C.
timeSignificance
Indicates the degree to which a specific point or interval in time is important, impactful, or meaningful within a given context.
-
D.
notableFrequency
Indicates that an action, event, or occurrence happens with a frequency that is significant or noteworthy compared to typical expectations.
-
E.
notablePopularityPeriod
Indicates the time span during which something was especially popular or widely recognized.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbffda78819088bf8dbc61756831 |
completed | April 20, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:30 p.m.