Triple
T13144816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulawun |
E312308
|
entity |
| Predicate | hasSymmetricalProfile |
P50368
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ulawun, hasSymmetricalProfile, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSymmetricalProfile Context triple: [Ulawun, hasSymmetricalProfile, yes]
-
A.
isSymmetrical
chosen
Indicates that an object, pattern, or configuration remains unchanged or mirrored when transformed by a symmetry operation such as reflection, rotation, or inversion.
-
B.
isSymmetricAbout
Indicates that one entity is a mirror image of another with respect to a specified axis, point, or plane of symmetry.
-
C.
isSymmetric
Indicates that a relationship holds in both directions between two entities, so if it applies from A to B, it also applies from B to A.
-
D.
hasSymmetryType
Indicates that one entity possesses a specific kind or pattern of symmetry characterized or classified by the other entity.
-
E.
testsSymmetry
Indicates that one entity evaluates or verifies whether a relationship or property holds identically in both directions between two entities.
- 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bbd1d088190b7c69f37fc6eeb64 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:10 p.m.