Triple
T25079873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government of Sint Maarten |
E628154
|
entity |
| Predicate | sharedCompetence |
P144537
|
FINISHED |
| Object | defence |
—
|
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: defence | Statement: [Government of Sint Maarten, sharedCompetence, defence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharedCompetence Context triple: [Government of Sint Maarten, sharedCompetence, defence]
-
A.
sharesCompetencesWith
Indicates that two entities possess and can apply the same or overlapping set of skills, abilities, or areas of expertise.
-
B.
competence
Indicates that an entity has the ability, skill, or qualification to perform a task or fulfill a role effectively.
-
C.
concurrentCompetenceArea
chosen
Indicates that two or more competence areas are active or applicable at the same time in relation to the same context, task, or entity.
-
D.
supportsCompetency
Indicates that one entity provides the basis, evidence, or reinforcement for the development, validation, or demonstration of a particular competency.
-
E.
sharesComplexWith
Indicates that two entities are components of, or co-residents within, the same larger complex or composite structure.
- 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_69e2ff2e73f881909992bf3eda5c25cb |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 18, 2026, 6:22 a.m.