Triple
T36640635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | symmetric group S5 |
E904572
|
entity |
| Predicate | hasNaturalAction |
P200356
|
FINISHED |
| Object | on a 5‑element set |
—
|
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: on a 5‑element set | Statement: [symmetric group S5, hasNaturalAction, on a 5‑element set]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNaturalAction Context triple: [symmetric group S5, hasNaturalAction, on a 5‑element set]
-
A.
hasNaturalActionBy
Indicates that one entity inherently performs, exhibits, or undergoes a characteristic action in relation to another entity.
-
B.
hasNaturalRole
Indicates that an entity inherently fulfills or is assigned a particular function, purpose, or role within a natural or conceptual system.
-
C.
hasNaturalCondition
Indicates that an entity possesses or is subject to a particular natural state, feature, or condition inherent to its environment or biology.
-
D.
hasNaturalContext
Indicates that something exists or occurs within a relevant real-world or naturally occurring situation or environment.
-
E.
hasNaturalForm
Indicates that an entity possesses an inherent, unaltered, or naturally occurring form or state.
- F. None of above. chosen
Provenance (4 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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff84202eb081908ae21a54a4414d68 |
completed | May 9, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69ff833065e4819098579129d4ee17d3 |
completed | May 9, 2026, 6:55 p.m. |
| PDg | Predicate description generation | batch_69ff841f2f2081908d72d4f878c538a0 |
completed | May 9, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:11 p.m.