Triple
T18673634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eclipse (yacht) |
E456543
|
entity |
| Predicate | hasArmorPlating |
P132245
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Eclipse (yacht), hasArmorPlating, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArmorPlating Context triple: [Eclipse (yacht), hasArmorPlating, true]
-
A.
armourThickness
Indicates the measured thickness of an entity’s protective armor in the context of defense or shielding.
-
B.
hasTypicalArmor
Indicates that an entity normally wears or is equipped with a standard or characteristic type of armor.
-
C.
armourProtection
Indicates that one entity provides protective armor or defensive covering for another entity.
-
D.
hasExplosiveReactiveArmor
Indicates that the subject is equipped with explosive reactive armor as a protective defensive feature.
-
E.
armourBelt
Indicates a relationship where an armour belt is equipped on, attached to, or associated with an entity (such as a character, vehicle, or structure) as protective gear.
- 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_69d8d38f72b4819090a935175d9ca8af |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e556b41cd881908f37bf7c85e96559 |
completed | April 19, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484133ee48190a80f1889d79f34c9 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:48 a.m.