Triple
T19632726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goan Catholic |
E471310
|
entity |
| Predicate | historicalConversionPeriod |
P24404
|
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: [Goan Catholic, historicalConversionPeriod, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalConversionPeriod Context triple: [Goan Catholic, historicalConversionPeriod, 16th century]
-
A.
historicalConversionFrom
Indicates a relationship where one entity was converted or transformed into another in the past, capturing a former state-to-state change over time.
-
B.
historicalSubunitToUnit
Indicates that one entity was historically a subunit, subdivision, or component of another larger entity.
-
C.
shareHistoricalUnionPeriod
Indicates that two entities were part of the same political or administrative union during an overlapping historical time period.
-
D.
eraOfConversion
chosen
Indicates the specific historical period or era during which the conversion event or change took place.
-
E.
historicalPartitionPeriod
Indicates that an entity existed, occurred, or is relevant during a specific historical period of territorial partition.
- 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_69d8e511f28481909f4bc3ea9191e54a |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6410449ec8190b8c20c0e09cd9156 |
completed | April 20, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.