Triple
T18772693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 4725 |
E459053
|
entity |
| Predicate | isAsymmetric |
P124554
|
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: [NGC 4725, isAsymmetric, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAsymmetric Context triple: [NGC 4725, isAsymmetric, yes]
-
A.
hasAsymmetry
chosen
Indicates that one entity exhibits a lack of symmetry or an uneven, non-mirrored relationship or structure relative to another entity.
-
B.
canBeAsymmetricBetween
Indicates that the relationship or property may hold in one direction between two entities without necessarily holding in the reverse direction.
-
C.
asymmetric
Indicates that the relationship between two entities never holds in both directions simultaneously, so if it holds from A to B it cannot also hold from B to A.
-
D.
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.
-
E.
hasGlobalAsymmetry
Indicates that an entity exhibits a non-uniform or directionally biased property or structure when considered at a global or overall scale.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e59336a6b08190819595a55177264e |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.