Triple
T14273914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Singapore Army |
E353866
|
entity |
| Predicate | equipmentIncludes |
P113532
|
FINISHED |
| Object | main battle tanks |
—
|
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: main battle tanks | Statement: [Singapore Army, equipmentIncludes, main battle tanks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equipmentIncludes Context triple: [Singapore Army, equipmentIncludes, main battle tanks]
-
A.
productIncludes
Indicates that a product contains, comprises, or is composed of the specified component, item, or feature.
-
B.
fleetIncludes
Indicates that a particular fleet contains or is composed of the specified entity or entities as its members.
-
C.
equipmentOption
Indicates that a particular piece or configuration of equipment is available or selected as an option in a given context.
-
D.
equipmentCharacteristic
Indicates that a specific characteristic, property, or attribute is associated with a piece of equipment.
-
E.
equippedFor
Indicates that one entity is suitably provided with the necessary tools, features, or capabilities to perform a particular function or handle a specific situation for another entity or purpose.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6582f5308190969f4cfd724d9139 |
completed | April 14, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69de2a88446481909cd526da97a3b70f |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:10 a.m.