Triple
T7488860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jutes |
E176950
|
entity |
| Predicate | approximateEndOfDistinctIdentity |
P35259
|
FINISHED |
| Object | early Middle Ages in England |
—
|
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: early Middle Ages in England | Statement: [Jutes, approximateEndOfDistinctIdentity, early Middle Ages in England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateEndOfDistinctIdentity Context triple: [Jutes, approximateEndOfDistinctIdentity, early Middle Ages in England]
-
A.
endOfDistinctIdentity
Indicates the point or condition at which a previously separate or distinguishable identity ceases to exist as a distinct entity.
-
B.
timePeriodEndApprox
chosen
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
C.
hasApproximateEnd
Indicates that an entity’s end point, time, or boundary is known only approximately rather than precisely.
-
D.
hasDistinctIdentity
Indicates that an entity possesses its own unique, distinguishable identity separate from other entities.
-
E.
endOf
Indicates that one entity marks the terminating point or final boundary of another entity, event, or interval.
- 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_69c69f24ac508190bb98fe927c0bd065 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f55abcd481909e42ca857fe46cd1 |
completed | March 27, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c6f03eeaa88190a5215772ed05ee9f |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:43 p.m.