Triple
T36494975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maeve Wiley |
E899159
|
entity |
| Predicate | coRuns |
P23427
|
FINISHED |
| Object | underground sex therapy clinic at Moordale Secondary School |
—
|
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: underground sex therapy clinic at Moordale Secondary School | Statement: [Maeve Wiley, coRuns, underground sex therapy clinic at Moordale Secondary School]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coRuns Context triple: [Maeve Wiley, coRuns, underground sex therapy clinic at Moordale Secondary School]
-
A.
odiRuns
Indicates the number of runs a player scores in One Day International (ODI) cricket matches.
-
B.
runsFrom
Indicates that one entity flees or escapes away from another entity.
-
C.
runs
Indicates that an entity moves swiftly on foot, typically using its legs in a continuous, rapid motion.
-
D.
alsoRuns
chosen
Indicates that the subject, in addition to its primary or previously mentioned activity or role, performs or operates another activity, process, or entity.
-
E.
runsVia
Indicates that a process, operation, or connection is executed, routed, or carried out through a specified intermediate channel, path, or mechanism.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.