Triple
T25842445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armidale-class patrol boat |
E650971
|
entity |
| Predicate | hasShipInClass |
P160292
|
FINISHED |
| Object | HMAS Ararat (ACPB 89) |
—
|
NE NERFINISHED |
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: HMAS Ararat (ACPB 89) | Statement: [Armidale-class patrol boat, hasShipInClass, HMAS Ararat (ACPB 89)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShipInClass Context triple: [Armidale-class patrol boat, hasShipInClass, HMAS Ararat (ACPB 89)]
-
A.
hasShipInClass
chosen
Indicates that an entity possesses or includes at least one ship that belongs to a specified ship class.
-
B.
hasShipCategory
Indicates that an entity is associated with or classified under a particular category or type of ship.
-
C.
hasShipRole
Indicates that an entity holds or is assigned a specific role or function on a ship.
-
D.
supportsClassOfShip
Indicates that one entity is capable of accommodating, servicing, or otherwise functionally supporting a specified class of ship.
-
E.
hasShipTypeCharacteristic
Indicates that a ship possesses a specific characteristic or property related to its type.
- 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_69e7ab38086081908f3a8e7e0c6efd83 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 22, 2026, 7:50 a.m.