Triple
T16893372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andamanese |
E424231
|
entity |
| Predicate | hasContactHistory |
P4255
|
FINISHED |
| Object | colonial contact with British Empire |
—
|
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 contact with British Empire | Statement: [Andamanese, hasContactHistory, colonial contact with British Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContactHistory Context triple: [Andamanese, hasContactHistory, colonial contact with British Empire]
-
A.
historicalContactWith
chosen
Indicates that two entities have interacted or been in communication with each other at some point in the past.
-
B.
hasHistoryIn
Indicates that an entity has a past involvement, presence, or record of activity within a particular domain, context, or location.
-
C.
hasHistoryOf
Indicates that an entity has a documented prior occurrence or background of a specified condition, event, or state.
-
D.
hasTransportHistory
Indicates that there exists a record or sequence of past transportation-related events or movements associated with an entity.
-
E.
hasTransportHistoryAs
Indicates that an entity has a record or log of being transported, characterized or classified in a specific way.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3bbc6b97c8190b18aca477d6ef647 |
completed | April 18, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69e32b90ec3c819099c51bb7baf2984c |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:29 a.m.