Triple
T25418921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMAS Ballarat (FFH 155) |
E636921
|
entity |
| Predicate | allianceDesign |
P158487
|
FINISHED |
| Object | based on MEKO 200 design |
—
|
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: based on MEKO 200 design | Statement: [HMAS Ballarat (FFH 155), allianceDesign, based on MEKO 200 design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allianceDesign Context triple: [HMAS Ballarat (FFH 155), allianceDesign, based on MEKO 200 design]
-
A.
allianceDesignation
Indicates a formal relationship in which one entity designates or classifies another as an ally within an alliance.
-
B.
allianceDesignationSystem
Indicates a system that defines, assigns, or manages formal alliance designations between entities.
-
C.
allianceProject
Indicates a collaborative project or initiative jointly undertaken by allied entities within an alliance relationship.
-
D.
allianceBrandOf
Indicates a relationship where one brand is part of, or operates under, a broader alliance or group brand.
-
E.
appliedInAlliance
Indicates that something (such as a method, strategy, or resource) is used or implemented within the context of an alliance or partnership between parties.
- F. None of above. chosen
Provenance (4 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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 1:55 p.m.