Triple
T33731301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darksaber |
E864281
|
entity |
| Predicate | ownershipRule |
P181787
|
FINISHED |
| Object | must be won in combat |
—
|
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: must be won in combat | Statement: [Darksaber, ownershipRule, must be won in combat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownershipRule Context triple: [Darksaber, ownershipRule, must be won in combat]
-
A.
ownershipConfers
Indicates that possessing or owning something grants the owner certain rights, powers, or privileges over it.
-
B.
ownershipPattern
Indicates the characteristic way in which ownership of something is structured, distributed, or shared among entities.
-
C.
ownershipRecord
Indicates that there exists a documented relationship specifying which entity legally owns or possesses another entity, typically including details such as owner, owned item, and relevant terms or period of ownership.
-
D.
ownershipType
Indicates the specific nature or category of the ownership relationship that one entity holds over another.
-
E.
ownershipStart
Indicates the point in time at which an entity begins to own or hold legal possession of another entity.
- F. None of above. chosen
Provenance (4 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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7824dc3f0819092a5102895b4a478 |
completed | May 3, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f7817c79e081908e685c48165e086b |
completed | May 3, 2026, 5:10 p.m. |
Created at: May 1, 2026, 1:44 a.m.