Triple
T15539230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tupiniquim |
E370431
|
entity |
| Predicate | timeOfFirstRecordedContact |
P79627
|
FINISHED |
| Object | 16th 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: 16th century | Statement: [Tupiniquim, timeOfFirstRecordedContact, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfFirstRecordedContact Context triple: [Tupiniquim, timeOfFirstRecordedContact, 16th century]
-
A.
dateOfFirstMeeting
Indicates the specific date on which two or more entities first met or came together.
-
B.
firstReachedDate
Indicates the date on which a particular entity first achieved, accessed, or arrived at a specified state, location, or milestone.
-
C.
historicalContactWith
Indicates that two entities have interacted or been in communication with each other at some point in the past.
-
D.
firstIntroductionDate
Indicates the date on which an entity was first introduced or presented for the first time.
-
E.
firstDetectedOn
chosen
Indicates the date or time when something was initially observed, discovered, or recorded for the first time.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04430b5188190a555a3cd4fb0c61c |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:07 a.m.