Triple
T16741054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Tank Corps |
E406833
|
entity |
| Predicate | notableEquipmentClass |
P97143
|
FINISHED |
| Object | 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: tanks | Statement: [Australian Tank Corps, notableEquipmentClass, tanks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEquipmentClass Context triple: [Australian Tank Corps, notableEquipmentClass, tanks]
-
A.
notableArmor
Indicates that an entity is recognized for possessing or being associated with armor of particular significance, prominence, or distinction.
-
B.
notableRaceClass
Indicates that there exists a notable race or competition of a particular class or category associated with the subject.
-
C.
oftenEquippedWith
chosen
Indicates that one type of entity is frequently or typically outfitted, furnished, or supplied with another entity.
-
D.
hasNotableWeaponNamedAfter
Indicates that an entity possesses a notable weapon that is named after another specific entity.
-
E.
notableFeat
Indicates that an entity is recognized for having achieved or performed a particularly significant or distinguished feat.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e39c3e87348190acaf7c40e8f8b566 |
completed | April 18, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.