Triple
T21121516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Grazia |
E520441
|
entity |
| Predicate | hasNotableUsePeriod |
P4017
|
FINISHED |
| Object | historical use for religious retreats |
—
|
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: historical use for religious retreats | Statement: [La Grazia, hasNotableUsePeriod, historical use for religious retreats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableUsePeriod Context triple: [La Grazia, hasNotableUsePeriod, historical use for religious retreats]
-
A.
hasNotabilityPeriod
Indicates the time span during which an entity is or was notable or prominent.
-
B.
periodOfMajorUse
chosen
Indicates the time span during which something was primarily or most intensively used.
-
C.
hasTypicalUseTime
Indicates the usual or expected duration or time period during which something is commonly used or in operation.
-
D.
hasNotableRecordingPeriod
Indicates that an entity is associated with a specific time span during which notable recording activity took place.
-
E.
hasTemporalUse
Indicates that something is used, applicable, or valid only during a specific time or temporal interval.
- 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_69e0b50a623881909c0bbaf4f2c055e7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e722348fe08190a1f079b7b0b5dd14 |
completed | April 21, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:55 p.m.