Triple
T28874881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pusat Latihan Kapal Selam |
E732237
|
entity |
| Predicate | focusesOnPlatformType |
P175981
|
FINISHED |
| Object | submarines |
—
|
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: submarines | Statement: [Pusat Latihan Kapal Selam, focusesOnPlatformType, submarines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusesOnPlatformType Context triple: [Pusat Latihan Kapal Selam, focusesOnPlatformType, submarines]
-
A.
focusesOnPlatform
chosen
Indicates that an entity’s attention, effort, or activity is primarily directed toward a particular platform as its main context or target.
-
B.
usedOnPlatformType
Indicates that something is utilized or operates on a specific type of platform.
-
C.
hasPlatformType
Indicates that an entity is associated with or characterized by a specific type or category of platform.
-
D.
usedPlatformType
Indicates that an entity makes use of or operates on a particular type or category of platform.
-
E.
consideredPlatform
Indicates that one entity is regarded or treated as a platform (e.g., a base, medium, or environment) for another entity or activity.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 28, 2026, 7:37 a.m.