Triple
T8322142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sacred Spring |
E194857
|
entity |
| Predicate | hasEraOfMajorDevelopment |
P95
|
FINISHED |
| Object | Roman 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: Roman period | Statement: [Sacred Spring, hasEraOfMajorDevelopment, Roman period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEraOfMajorDevelopment Context triple: [Sacred Spring, hasEraOfMajorDevelopment, Roman period]
-
A.
historicalPeriodOfMajorActivity
Indicates the historical period during which an entity carried out its most significant or influential activities.
-
B.
wasDevelopedInPeriod
chosen
Indicates that something was created, produced, or brought into existence during a specified time period.
-
C.
historicalEraUsheredIn
Indicates the historical era or period that was initiated or brought about as a result of a particular event, action, or entity.
-
D.
urbanDevelopmentEra
Indicates the historical period or phase during which significant urban development or transformation of a place occurred.
-
E.
historicalEraOfSuccess
Indicates that an entity achieved notable success or prominence during a specified historical era.
- 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_69ca82e7a8a88190a32bb5cc0feb012d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f693ad08190ad4ce6269a61eb3f |
completed | March 31, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69cb70bf689c8190a9d9b6b872abf53d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:55 p.m.