Triple
T11756497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foudroyant (French ship) |
E279538
|
entity |
| Predicate | armamentConfiguration |
P101195
|
FINISHED |
| Object | two-decker |
—
|
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: two-decker | Statement: [Foudroyant (French ship), armamentConfiguration, two-decker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armamentConfiguration Context triple: [Foudroyant (French ship), armamentConfiguration, two-decker]
-
A.
armamentFlexible
Indicates that an entity’s armament or weapon configuration can be adjusted, reconfigured, or adapted to different setups or roles.
-
B.
armamentStatus
Indicates the current condition or readiness level of an entity’s weapons or military equipment.
-
C.
armamentCategory
Indicates the classification of a weapon or military equipment according to its type or role in armament systems.
-
D.
armamentCapacity
Indicates the maximum quantity or type of weapons or munitions that something is designed or allowed to carry.
-
E.
enhancedArmament
Indicates that an entity’s weaponry or combat equipment has been upgraded, augmented, or otherwise improved beyond its standard configuration.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a50c8d708190ad79ecb57b715d04 |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a829fe481909cc5431de7d6058e |
completed | April 10, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69d890467a2481909ce6c669e739c8de |
completed | April 10, 2026, 5:53 a.m. |
Created at: April 8, 2026, 9:41 p.m.