Triple
T38402703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muhaarar |
E900942
|
entity |
| Predicate | stud |
P190844
|
FINISHED |
| Object | Nunnery Stud |
—
|
NE NERFINISHED |
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: Nunnery Stud | Statement: [Muhaarar, stud, Nunnery Stud]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stud Context triple: [Muhaarar, stud, Nunnery Stud]
-
A.
study
Indicates engaging in a systematic effort to learn, understand, or investigate a subject or object.
-
B.
studType
Indicates a relationship where an entity is classified as a particular type or category of stud (e.g., a specific kind of fastener or structural element).
-
C.
studiesFor
Indicates that one entity engages in studying or academic preparation with the purpose of achieving or supporting another entity (such as a goal, exam, or qualification).
-
D.
studDuty
Indicates that an entity has a duty, responsibility, or obligation related to studying or academic work.
-
E.
studyUnit
Indicates a relationship where an entity is a unit, module, or component of study within a broader course, curriculum, or learning program.
- 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_69f76e6071a081909eea7a670d21420c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
| PDg | Predicate description generation | batch_69fcd148e6d4819082c118832ecc599b |
completed | May 7, 2026, 5:52 p.m. |
Created at: May 3, 2026, 4:31 p.m.