Triple
T17746682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Watchers Council |
E443006
|
entity |
| Predicate | Cruciamentum testFor |
P128630
|
FINISHED |
| Object | Slayer at age 18 |
—
|
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: Slayer at age 18 | Statement: [Watchers Council, Cruciamentum testFor, Slayer at age 18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Cruciamentum testFor Context triple: [Watchers Council, Cruciamentum testFor, Slayer at age 18]
-
A.
testedFor
Indicates that an entity has been examined or analyzed to determine the presence, absence, or level of another specified entity or condition.
-
B.
containsTest
Indicates that one entity includes or encompasses another entity as a test or testing component.
-
C.
commonTest
Indicates that two or more entities share the same test, testing procedure, or evaluation in common.
-
D.
test
Indicates that an entity performs, undergoes, or is associated with a testing or examination process involving another entity or condition.
-
E.
testsIn
Indicates that one entity conducts or performs tests within, on, or using 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47ad26940819090696c2cb86fd606 |
completed | April 19, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69e3cde9dc288190af0e2198487f2051 |
completed | April 18, 2026, 6:31 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 10:09 a.m.