Triple
T27594491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osian |
E699857
|
entity |
| Predicate | historicalEraOfMajorMonuments |
P68750
|
FINISHED |
| Object | early 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: early medieval period | Statement: [Osian, historicalEraOfMajorMonuments, early medieval period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalEraOfMajorMonuments Context triple: [Osian, historicalEraOfMajorMonuments, early medieval period]
-
A.
eraOfOriginalMonuments
chosen
Indicates the historical time period during which the original monuments were created or first established.
-
B.
hasMonumentInPeriod
Indicates that a monument is associated with or existed during a specified time period.
-
C.
historicalStructure
Indicates that the subject is a structure recognized for its historical significance or heritage value.
-
D.
historicalPeriodOfSignificance
Indicates the time period during which an entity is considered to have had its most important or influential historical impact.
-
E.
knownMonuments
Indicates that an entity is recognized or identified as a monument by another entity or within a given context.
- 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_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: April 27, 2026, 2:06 p.m.