Triple
T22047761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jogyesa Temple |
E544805
|
entity |
| Predicate | hasCourtyardTree |
P6742
|
FINISHED |
| Object | large locust tree |
—
|
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: large locust tree | Statement: [Jogyesa Temple, hasCourtyardTree, large locust tree]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCourtyardTree Context triple: [Jogyesa Temple, hasCourtyardTree, large locust tree]
-
A.
hasCourtyard
Indicates that one entity includes, features, or is characterized by the presence of a courtyard.
-
B.
hasCourtyardFeature
Indicates that a courtyard possesses or includes a specific feature or characteristic.
-
C.
hasCourtyardArea
Indicates that an entity includes or is associated with a courtyard and specifies the size or extent of that courtyard space.
-
D.
hasCourtyardUse
Indicates that one entity is permitted or designated to use the courtyard of another entity.
-
E.
hasTrees
chosen
Indicates that something possesses or contains one or more trees.
- 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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12830c674819080254d77ee02bc9f |
completed | April 28, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e6f643ca74819083e8ab78e843f243 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:26 p.m.