Triple
T4248407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High German consonant shift |
E95783
|
entity |
| Predicate | startsAround |
P39845
|
FINISHED |
| Object | late 3rd 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: late 3rd century | Statement: [High German consonant shift, startsAround, late 3rd century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startsAround Context triple: [High German consonant shift, startsAround, late 3rd century]
-
A.
occursOnOrAround
chosen
Indicates that an event or action takes place on a specific date or within a small, approximate time window surrounding that date.
-
B.
runsAround
Indicates that one entity moves in a circular or surrounding path around another entity or area.
-
C.
activeAround
Indicates that an entity is performing actions or exhibiting activity in the vicinity of another entity or location.
-
D.
surrounds
Indicates that one entity is located all around another entity, enclosing or encircling it on multiple sides or completely.
-
E.
around
Indicates that one entity is located or moves on all or most sides of another entity, encircling or surrounding it spatially.
- 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_69b3453f759881909b91f01a1e82c036 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e9cb71481909b4baa370193148f |
completed | March 12, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69b347f73e008190a908a48ef389945a |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:06 p.m.