Triple
T29654731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conclave |
E750234
|
entity |
| Predicate | ordersArrestOf |
P22280
|
FINISHED |
| Object | Tassadar |
—
|
NE NERFINISHED |
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: Tassadar | Statement: [Conclave, ordersArrestOf, Tassadar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ordersArrestOf Context triple: [Conclave, ordersArrestOf, Tassadar]
-
A.
arrestIs
Indicates that one entity performs the action of arresting or taking another entity into legal custody.
-
B.
arrests
chosen
Indicates that one entity, typically an authority figure, seizes and detains another entity under legal or official power.
-
C.
arrestedFor
Indicates that an authority has taken someone into custody because they are suspected or accused of committing a specified offense or wrongdoing.
-
D.
arrestedWith
Indicates that two or more individuals were arrested at the same time and in connection with the same incident or operation.
-
E.
attemptedArrestBy
Indicates that one entity tried, but may not have succeeded, to place another entity under arrest.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 28, 2026, 6:54 p.m.