Triple
T4561860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lesser Mysteries |
E121809
|
entity |
| Predicate | requiredStatus |
P43873
|
FINISHED |
| Object | mystai |
—
|
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: mystai | Statement: [Lesser Mysteries, requiredStatus, mystai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredStatus Context triple: [Lesser Mysteries, requiredStatus, mystai]
-
A.
requiresStatus
chosen
Indicates that one entity can only proceed, be valid, or be applied if another entity has a specified status or condition.
-
B.
requiredBy
Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
-
C.
establishedRequirement
Indicates that one entity has formally set or defined a requirement that another entity is expected to satisfy or comply with.
-
D.
hasProfessionalStatusRequirement
Indicates that something is subject to a condition specifying a particular professional status that must be held or met.
-
E.
registrationRequirement
Indicates that an entity is obligated to formally register with a specified authority, system, or registry under certain conditions.
- 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_69bd463f156881908a99aca69c5721ac |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd582f21648190b49284eb61b618c9 |
completed | March 20, 2026, 2:22 p.m. |
| PD | Predicate disambiguation | batch_69bd52254c648190a5144cfe8fa7e409 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:09 p.m.