Triple
T26679252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anne de Mowbray, 8th Countess of Norfolk |
E672558
|
entity |
| Predicate | remainsDiscovered |
P126462
|
FINISHED |
| Object | 1964 |
—
|
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: 1964 | Statement: [Anne de Mowbray, 8th Countess of Norfolk, remainsDiscovered, 1964]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remainsDiscovered Context triple: [Anne de Mowbray, 8th Countess of Norfolk, remainsDiscovered, 1964]
-
A.
remainsDiscoveredBy
Indicates that physical remains (such as fossils, artifacts, or bodies) were found or uncovered by a particular discoverer or discovering entity.
-
B.
remainsDiscoveredOn
chosen
Indicates that the physical remains of an entity were found or uncovered at a particular location or site.
-
C.
hasDiscovered
Indicates that one entity has found, detected, or uncovered the existence, presence, or truth of another entity or phenomenon.
-
D.
laterDiscovered
Indicates that one entity was discovered or found at a time subsequent to the discovery of another entity.
-
E.
discoveredAs
Indicates that one entity was first identified, found, or recognized in the role or form specified by another entity.
- 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_69eecda13424819092b17942c4edf722 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f617060fc8819095d063081288880d |
completed | May 2, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:18 a.m.