Triple
T30043194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mighty A |
E763372
|
entity |
| Predicate | associatedWithCurrentUse |
—
|
GENERATED |
| Object | museum ship |
—
|
UNRECOGNIZED 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: associatedWithCurrentUse Context triple: [Mighty A, associatedWithCurrentUse, museum ship]
-
A.
associatedWithUse
chosen
Indicates a relationship where one entity is connected to or involved in the use or utilization of another entity.
-
B.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
-
C.
associatedCurrent
Indicates a relationship where a particular current is linked or connected to another entity as its relevant or corresponding current.
-
D.
endedUseWith
Indicates that an entity has stopped or terminated its use or association with another entity.
-
E.
usedToOperateInConjunctionWith
Indicates that one entity was formerly operated together with another entity as part of a combined or coordinated functioning.
- F. None of above.
Provenance (1 batch)
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_69f22470a89c8190be7273297c0e0d19 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 6:53 p.m.