Triple
T10597089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Desert Rats |
E250142
|
entity |
| Predicate | appliesToFormationNumber |
P94847
|
FINISHED |
| Object | 7th |
—
|
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: 7th | Statement: [Desert Rats, appliesToFormationNumber, 7th]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToFormationNumber Context triple: [Desert Rats, appliesToFormationNumber, 7th]
-
A.
containsFormation
Indicates that one entity spatially or structurally includes or encloses a formation as part of its extent or composition.
-
B.
supportedFormation
Indicates that one entity provided assistance, resources, or conditions that enabled the creation or establishment of another entity or structure.
-
C.
supportedFormationType
Indicates the type of formation that an entity is capable of supporting or is designed to work with.
-
D.
isFormedFor
Indicates that something is created, established, or brought into existence for a particular purpose, function, or beneficiary.
-
E.
hasFieldFormation
Indicates that an entity possesses or exhibits a particular field formation, such as a structured arrangement or configuration of fields.
- 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5278e5d5481908f4e19c52bd80327 |
completed | April 7, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69d5190a6dfc819088262957551808a1 |
completed | April 7, 2026, 2:47 p.m. |
| PDg | Predicate description generation | batch_69d5270eca0481908573b698390c5b08 |
completed | April 7, 2026, 3:47 p.m. |
Created at: April 6, 2026, 12:41 p.m.