Triple
T32792095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horyuji Homotsukan |
E838655
|
entity |
| Predicate | primarySourceOfCollection |
P10914
|
FINISHED |
| Object | Horyu-ji Temple |
E144089
|
NE 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: Horyu-ji Temple | Statement: [Horyuji Homotsukan, primarySourceOfCollection, Horyu-ji Temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySourceOfCollection Context triple: [Horyuji Homotsukan, primarySourceOfCollection, Horyu-ji Temple]
-
A.
primaryCollectionOf
Indicates that one entity serves as the main or principal collection to which another entity primarily belongs or is associated.
-
B.
primarySources
Indicates that one entity serves as an original, authoritative source of information or evidence for another entity.
-
C.
collectionOrigin
chosen
Indicates that one entity is the source, provenance, or originating context from which a collection of items or data has been derived or assembled.
-
D.
primarySourceArea
Indicates that something originates from, or is chiefly derived from, a specified source area.
-
E.
primarySourcesLocation
Indicates the place where the original or primary source materials related to an entity are held or can be accessed.
- F. None of above.
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_69f3493c7f6881908edf2aa13631d1e0 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37bcf282f881909c8075a250d908b2 |
completed | June 21, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:14 a.m.