Triple
T38697870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of Derby |
E950053
|
entity |
| Predicate | aroseAfter |
P6702
|
FINISHED |
| Object | Norman Conquest of England |
—
|
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: Norman Conquest of England | Statement: [Lord of Derby, aroseAfter, Norman Conquest of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aroseAfter Context triple: [Lord of Derby, aroseAfter, Norman Conquest of England]
-
A.
arisesAfter
Indicates that one event, state, or condition comes into existence or begins only after another specified event, state, or condition has occurred.
-
B.
alsoArisesAfter
Indicates that one event, condition, or state occurs as an additional outcome following another event, condition, or state in time.
-
C.
raisedAfter
Indicates that one entity was raised or brought up at a later time than another entity.
-
D.
tookPlaceAfter
chosen
Indicates that one event or occurrence happened later in time than another event or occurrence.
-
E.
laterRaised
Indicates that one entity was raised, elevated, or brought up at a time subsequent to another referenced event or state.
- 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_69f76f0124408190bb39c3040734846b |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:33 p.m.