Triple
T38368490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beskar |
E892515
|
entity |
| Predicate | tradeControlledBy |
P76272
|
FINISHED |
| Object | Mandalorian clans |
—
|
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: Mandalorian clans | Statement: [Beskar, tradeControlledBy, Mandalorian clans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradeControlledBy Context triple: [Beskar, tradeControlledBy, Mandalorian clans]
-
A.
isControlledUnder
Indicates that one entity is subject to regulatory, legal, or authoritative control exercised by another entity or governing framework.
-
B.
controlledTradeWith
chosen
Indicates a regulated or restricted trading relationship in which one entity manages, oversees, or limits the trade activities conducted with another entity.
-
C.
isUnderControlOf
Indicates that one entity is subject to the authority, direction, or governance of another entity.
-
D.
controlsOrControlled
Indicates that one entity has control over another entity or is itself under the control of that other entity.
-
E.
exertsControlOver
Indicates that one entity has the power or authority to direct, influence, or determine the actions or decisions of another entity.
- 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_69f76e47cb4c8190bdd92cd1db59c0c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.