Triple
T888873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Forces Tab |
E19192
|
entity |
| Predicate | relatedInsignia |
P37
|
FINISHED |
| Object | Ranger Tab |
—
|
NE GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedInsignia Context triple: [Special Forces Tab, relatedInsignia, Ranger Tab]
-
A.
relatedBrand
Indicates a relationship where one brand is associated with, connected to, or otherwise related to another brand.
-
B.
relatedTo
chosen
Indicates a general, non-specific relationship or association exists between two entities.
-
C.
relatedService
Indicates that one service is connected or associated with another service in a relevant or dependent way.
-
D.
associatedFranchise
Indicates a relationship where one entity is linked to, or belongs within, a particular franchise or franchise universe.
-
E.
relatedStyle
Indicates that one style is associated with, similar to, or derived from another style in some relevant way.
- F. None of above.
Provenance (2 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_69a4939c32488190a7ccd41cf0abb22b |
completed | March 1, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69a4aa9227ec8190a726456fc77c3ebb |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.