Triple
T7906386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lisle Von Rhoman |
E183586
|
entity |
| Predicate | givesConditionForPotion |
P56247
|
FINISHED |
| Object | secrecy about the potion |
—
|
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: secrecy about the potion | Statement: [Lisle Von Rhoman, givesConditionForPotion, secrecy about the potion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: givesConditionForPotion Context triple: [Lisle Von Rhoman, givesConditionForPotion, secrecy about the potion]
-
A.
definesConditionsFor
chosen
Indicates that one entity specifies or establishes the rules, requirements, or circumstances under which another entity is valid, applicable, or operates.
-
B.
fieldTincture
Indicates the heraldic tincture (color, metal, or fur) applied to the main background field of a coat of arms.
-
C.
hasCondition
Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
-
D.
varietyCondition
Indicates a condition, constraint, or context under which a particular variety or variant of something applies or is relevant.
-
E.
minimumBottlingStrength
Indicates the lowest alcohol strength at which a beverage is allowed or intended to be bottled.
- 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_69ca828dec0c81908b8f55a4dbbb53ff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a5871b8819087ad69c116c40091 |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae92f9498819085277879e59aa072 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:03 p.m.