Triple
T20983338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | We'll Make It |
E516823
|
entity |
| Predicate | canBeEquippedIn |
P94968
|
FINISHED |
| Object | survivor loadout |
—
|
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: survivor loadout | Statement: [We'll Make It, canBeEquippedIn, survivor loadout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeEquippedIn Context triple: [We'll Make It, canBeEquippedIn, survivor loadout]
-
A.
oftenEquippedWith
Indicates that one type of entity is frequently or typically outfitted, furnished, or supplied with another entity.
-
B.
mayBeWorn
chosen
Indicates that one entity is suitable or allowed to be worn by another entity, typically as clothing, accessories, or adornment.
-
C.
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.
-
D.
crewEquipment
Indicates that certain equipment is assigned to, used by, or associated with a specific crew.
-
E.
canBeHeldWith
Indicates that two entities are compatible or suitable to be held or used together at the same time.
- 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_69e0b4ffac148190bbade9f0eceb660b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fbe03244819097630333e70c4e88 |
completed | April 21, 2026, 4:24 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:48 p.m.