Triple
T17145396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Java Hindu-Buddhist temple landscape |
E416077
|
entity |
| Predicate | hasMajorPeriod |
P28924
|
FINISHED |
| Object | 8th 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: 8th century | Statement: [Central Java Hindu-Buddhist temple landscape, hasMajorPeriod, 8th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorPeriod Context triple: [Central Java Hindu-Buddhist temple landscape, hasMajorPeriod, 8th century]
-
A.
hasMainPeriod
chosen
Indicates that something is associated with or characterized by a primary or most significant time period.
-
B.
hasMajor
Indicates that an entity (typically a person or student) has a specific primary field of academic study or specialization.
-
C.
hasMajorCategory
Indicates that something is associated with or classified under a primary, overarching category.
-
D.
hasMajorPass
Indicates that an entity possesses or is associated with a primary or significant pass (such as a main route, credential, or access authorization).
-
E.
isMajor
Indicates that an entity holds primary or greater significance, importance, or rank relative to others in a given context.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f2da515481909d19e421382eb755 |
completed | April 18, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.