Triple
T19507193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monastery of Sint Agatha |
E488052
|
entity |
| Predicate | hasApproximateStartOfUse |
P84680
|
FINISHED |
| Object | late 14th 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 14th century | Statement: [Monastery of Sint Agatha, hasApproximateStartOfUse, late 14th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateStartOfUse Context triple: [Monastery of Sint Agatha, hasApproximateStartOfUse, late 14th century]
-
A.
hasApproximateUse
Indicates that one entity is used for a purpose that is similar to, but not exactly the same as, the use or function of another entity.
-
B.
hasApproximatePublicationStart
Indicates that an entity is associated with an estimated or imprecise starting date for its publication.
-
C.
areUsedSince
Indicates that entities have been in use continuously starting from a specified point in time.
-
D.
hasTypicalUseTime
Indicates the usual or expected duration or time period during which something is commonly used or in operation.
-
E.
hasApproxGregorianStart
chosen
Indicates that an entity has an associated start date expressed as an approximate value in the Gregorian calendar.
- 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_69d8e8d9d1c88190b01cd78b8be49384 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e635130e708190bb3d70e1abbade2a |
completed | April 20, 2026, 2:15 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7bd25881908caa04eaef1f6718 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:40 p.m.