Triple
T5402155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prove Thyself |
E120801
|
entity |
| Predicate | stackingRule |
P51045
|
FINISHED |
| Object | Does not stack with other copies of Prove Thyself |
—
|
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: Does not stack with other copies of Prove Thyself | Statement: [Prove Thyself, stackingRule, Does not stack with other copies of Prove Thyself]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stackingRule Context triple: [Prove Thyself, stackingRule, Does not stack with other copies of Prove Thyself]
-
A.
stackingConfiguration
chosen
Indicates how multiple entities are arranged or layered on top of each other in a specific order or configuration.
-
B.
compositionRule
Indicates how multiple elements or components are combined or arranged according to a specific rule or pattern.
-
C.
displayRule
Indicates the rule or condition that determines how something should be visually presented or displayed.
-
D.
styleOfRule
Indicates the stylistic or formatting convention that a particular rule follows or is expressed in.
-
E.
usesRulesFrom
Indicates that one entity applies, follows, or is governed by the rules defined or provided by 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_69bd46391c0c81909fa484446732b6a3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8932b8bc8190bd31e11b167a7212 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd84660ea08190a641084814fcf94d |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:04 p.m.