Triple
T3024164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady Holy Church |
E82536
|
entity |
| Predicate | firstAppearsIn |
P29367
|
FINISHED |
| Object | the opening vision of Piers Plowman |
—
|
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: the opening vision of Piers Plowman | Statement: [Lady Holy Church, firstAppearsIn, the opening vision of Piers Plowman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstAppearsIn Context triple: [Lady Holy Church, firstAppearsIn, the opening vision of Piers Plowman]
-
A.
firstAppeared
Indicates the earliest known time or context in which an entity was introduced, observed, or came into existence.
-
B.
firstAppearanceFor
chosen
Indicates that an entity marks the initial occurrence or debut of another entity within a given context or medium.
-
C.
appearsIn
Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
-
D.
firstAppearedAt
Indicates the point in time or specific event at which an entity was first introduced, observed, or became known.
-
E.
firstAppearanceEpisode
Indicates the specific episode in which an entity (such as a character or item) is shown or mentioned for the first time.
- 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_69ad8b1fb34081908c1b873e2b7273e1 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9abac0288190a30b42674eea501f |
completed | March 8, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69ad961c430c8190ac48f2e3c7e7c649 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.