Triple
T2397115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Portuguese India Armada |
E47675
|
entity |
| Predicate | arrivalInIndia |
P37714
|
FINISHED |
| Object | 1498 |
—
|
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: 1498 | Statement: [First Portuguese India Armada, arrivalInIndia, 1498]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arrivalInIndia Context triple: [First Portuguese India Armada, arrivalInIndia, 1498]
-
A.
estimatedArrivalInAustralia
Indicates the expected date and/or time when an entity is predicted to arrive in Australia.
-
B.
arrivalInEurope
Indicates the event or state of something or someone reaching or entering a location within Europe.
-
C.
placeOfArrival
Indicates the location at which an entity or person arrives at the end of a journey, movement, or transfer.
-
D.
positionOnImmigration
Indicates a stance or viewpoint that an entity holds regarding immigration policies or issues.
-
E.
historicalPeriodOfArrival
chosen
Indicates the historical time period during which an entity arrived at or first appeared in a particular place or context.
- 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_69a88a1c450c81909f61abb8b6863885 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc8c4a8bc819086892a75caac0207 |
completed | March 7, 2026, 6:42 a.m. |
| PD | Predicate disambiguation | batch_69abc5a3825c81909ec6111dfc165453 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.