Triple
T9716680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Janus |
E235159
|
entity |
| Predicate | templeFeature |
P27591
|
FINISHED |
| Object | doors of his temple open in times of war |
—
|
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: doors of his temple open in times of war | Statement: [Janus, templeFeature, doors of his temple open in times of war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: templeFeature Context triple: [Janus, templeFeature, doors of his temple open in times of war]
-
A.
templeType
Indicates the specific category or classification of a temple in terms of its form, function, or religious/architectural style.
-
B.
typicalShrineFeature
chosen
Indicates that something is a characteristic or commonly found element of a shrine.
-
C.
mainTemple
Indicates that one entity serves as the primary or central temple associated with another entity.
-
D.
associatedTemple
Indicates a relationship where one entity is linked or connected to a particular temple, typically as its relevant or related religious site.
-
E.
majorTempleLocation
Indicates that a major temple associated with an entity is located at a specified place.
- 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_69ca84cd8fa0819090a5e243ceb37003 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9e3d75e08190b4d86363595bd40d |
completed | April 1, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69cd03bfeca08190924fca43aaa9c10f |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:20 p.m.