Triple
T3550758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Olympus National Monument |
E75104
|
entity |
| Predicate | incorporatedIntoOnDate |
P50534
|
FINISHED |
| Object | 1938-06-29 |
—
|
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: 1938-06-29 | Statement: [Mount Olympus National Monument, incorporatedIntoOnDate, 1938-06-29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incorporatedIntoOnDate Context triple: [Mount Olympus National Monument, incorporatedIntoOnDate, 1938-06-29]
-
A.
laterIncorporatedInto
Indicates that one entity was subsequently merged into, absorbed by, or formally made part of another entity at a later time.
-
B.
integrationDate
Indicates the date on which two or more entities, systems, or components are combined or brought into a unified whole.
-
C.
incorporatedThrough
Indicates that one entity was formed, established, or legally created by means of another specified process, mechanism, or intermediary entity.
-
D.
ordinationDate
Indicates the date on which an individual was formally ordained to a religious office or role.
-
E.
designationDate
Indicates the date on which an entity is formally assigned, designated, or given a particular status or role.
- F. None of above. chosen
Provenance (4 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_69ad85d33c6c819081d5ac1df13b5680 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbfd52f44819088e07139fe987e2a |
completed | March 8, 2026, 6:28 p.m. |
| PD | Predicate disambiguation | batch_69adb83270ac819083967db0570167d2 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adba25c66c81909a05a97327828c41 |
completed | March 8, 2026, 6:04 p.m. |
Created at: March 8, 2026, 3:20 p.m.