Triple
T5509063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ise Grand Shrine |
E144514
|
entity |
| Predicate | numberOfSubShrines |
P27588
|
FINISHED |
| Object | over 100 |
—
|
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: over 100 | Statement: [Ise Grand Shrine, numberOfSubShrines, over 100]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfSubShrines Context triple: [Ise Grand Shrine, numberOfSubShrines, over 100]
-
A.
numberOfShrines
chosen
Indicates the total count of shrines associated with a given entity or context.
-
B.
hasShrinesIn
Indicates that one entity possesses or maintains shrines that are located within the area or domain of another entity.
-
C.
enshrines
Indicates that one entity formally preserves, protects, or honors another by giving it a permanent, often sacred or legally recognized, status.
-
D.
hasSubTemple
Indicates that one temple includes or contains another temple as a subordinate or component temple within its structure or organization.
-
E.
hasMajorShrine
Indicates that one entity serves as a principal or primary shrine dedicated to another entity.
- 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_69c008f6b5048190a09064116062cf69 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f4a80d88190bab0056c4c78be93 |
completed | March 22, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69c01b07bde08190b3933b96bdc70dd5 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:33 p.m.