Triple
T37664098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Illager |
E937782
|
entity |
| Predicate | relatedMobType |
—
|
GENERATED |
| Object | Villager |
—
|
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: relatedMobType Context triple: [Illager, relatedMobType, Villager]
-
A.
associatedMob
chosen
Indicates a relationship where one entity is linked or connected to a particular mob (mobile entity), typically as its counterpart, partner, or related unit.
-
B.
relatedVehicle
Indicates that there exists an associated or connected vehicle that has a relevant relationship to the primary entity.
-
C.
mobilitySegment
Indicates a distinct portion or phase within a broader movement or travel activity, treated as a separate unit of mobility.
-
D.
transportationRelatedTo
Indicates a relationship where one entity is connected to another through transportation, such as serving as a means, mode, infrastructure, or service for moving people or goods.
-
E.
mobilityRole
Indicates the functional role or capacity an entity has in enabling, supporting, or performing movement or transportation.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.