Triple
T3693561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .dm |
E78399
|
entity |
| Predicate | intendedRegistrants |
P485
|
FINISHED |
| Object | individuals in Dominica |
—
|
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: individuals in Dominica | Statement: [.dm, intendedRegistrants, individuals in Dominica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedRegistrants Context triple: [.dm, intendedRegistrants, individuals in Dominica]
-
A.
welcomesParticipantsOf
Indicates that one entity receives or greets the participants associated with another entity in a friendly or accepting manner.
-
B.
relatedRegister
Indicates a relationship where one entity is associated with, linked to, or corresponds to a particular register or record in a system.
-
C.
attractsParticipantsFrom
Indicates that an event, activity, or organization draws or recruits participants originating from a specified place, group, or source.
-
D.
scopeOfRecipients
chosen
Indicates the range or group of recipients to whom something (such as information, communication, or benefits) is directed or applicable.
-
E.
invitesParticipationOf
Indicates that one entity actively requests or encourages another entity to take part in an activity, event, or process.
- 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_69ad85e3b1888190abc983e06968696d |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc4e9e4748190aa178692ef27e3a6 |
completed | March 8, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69adb84dc5808190850aa6975cb09e27 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:26 p.m.