Triple
T3163298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charbagh garden |
E66150
|
entity |
| Predicate | typicallyOriented |
P1101
|
FINISHED |
| Object | cardinal directions |
—
|
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: cardinal directions | Statement: [Charbagh garden, typicallyOriented, cardinal directions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyOriented Context triple: [Charbagh garden, typicallyOriented, cardinal directions]
-
A.
orientation
chosen
Indicates the relative directional alignment or facing of one entity with respect to another or to a reference frame.
-
B.
socialOrientation
Indicates the nature or direction of an entity’s social tendencies, such as how it typically relates to, interacts with, or aligns itself within social contexts or groups.
-
C.
orientationInducedBy
Indicates that the orientation of one entity is determined or caused by the orientation or configuration of another entity.
-
D.
valueOrientation
Indicates how an entity’s preferences, priorities, or attitudes are directed toward particular values or value systems.
-
E.
orientedParallelTo
Indicates that one entity is parallel to another with a specified or consistent direction or orientation.
- 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_69ad85850c1481908a9e9c6242238de2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada61a4b8481908897a8d39d94c2f4 |
completed | March 8, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfe0a948190928f2201d671c654 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.