Triple
T21024325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | India–Ceylon relations |
E517896
|
entity |
| Predicate | peopleToPeopleTie |
P15429
|
FINISHED |
| Object | tourism between India and Sri Lanka |
—
|
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: tourism between India and Sri Lanka | Statement: [India–Ceylon relations, peopleToPeopleTie, tourism between India and Sri Lanka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peopleToPeopleTie Context triple: [India–Ceylon relations, peopleToPeopleTie, tourism between India and Sri Lanka]
-
A.
peopleToPeopleLink
Indicates a relationship that connects one person to another person in some defined way.
-
B.
peopleToPeopleLinksInclude
Indicates that a relationship or connection between people includes or encompasses certain specified links between them.
-
C.
tieInWith
Indicates that one thing is connected, coordinated, or made consistent with another, often as part of a combined plan, theme, or schedule.
-
D.
typeOfTie
Indicates the specific kind or category of relationship or connection that exists between two entities.
-
E.
notableTie
chosen
Indicates a significant connection or association between entities that is noteworthy or distinguished in some 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_69e0b50262b081909bc488937145eb73 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc5f5bcc8190ab5fcc467703f0ef |
completed | April 21, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:55 p.m.