Triple
T31533028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Catherine’s Court |
E804529
|
entity |
| Predicate | hasEarlierOrigins |
P1614
|
FINISHED |
| Object | medieval period |
—
|
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: medieval period | Statement: [St Catherine’s Court, hasEarlierOrigins, medieval period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEarlierOrigins Context triple: [St Catherine’s Court, hasEarlierOrigins, medieval period]
-
A.
hasEarlierVersion
Indicates that one entity is an earlier or prior version of another entity in a version sequence.
-
B.
hasHistoricalOrigin
chosen
Indicates that something originated, was first established, or came into existence during a specific historical period or context.
-
C.
hasHistoricalPrecursor
Indicates that one entity existed earlier and served as a predecessor, model, or influential forerunner to the other in a historical context.
-
D.
developedBefore
Indicates that one entity was developed or created earlier in time than another entity.
-
E.
hasHistoricalOriginInYear
Indicates that something first originated, began, or came into existence in a specified calendar year.
- 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8055f8081908f635fe04654b5fe |
completed | May 3, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:02 p.m.