Triple
T2100971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morea |
E37090
|
entity |
| Predicate | usedAsNameFromCentury |
P11826
|
FINISHED |
| Object | 13th century |
—
|
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: 13th century | Statement: [Morea, usedAsNameFromCentury, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsNameFromCentury Context triple: [Morea, usedAsNameFromCentury, 13th century]
-
A.
usedAsFirstNameSinceCentury
Indicates that an entity has been used as a first name starting from a specified century.
-
B.
usedInCentury
Indicates that something (such as an object, practice, or concept) was in use during a specified century.
-
C.
usedSinceCentury
Indicates that something has been in use starting from a specified century.
-
D.
attestedFromCentury
chosen
Indicates the century from which there is evidence or documentation that something is known to exist or be in use.
-
E.
usedAsMintInCentury
Indicates that an entity functioned as a mint (coin-producing facility) during a specified century.
- 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abbabb512c819087b1d5ec8ef11e63 |
completed | March 7, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69abb7b6274081909df36cd7a7c6a675 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.