Triple
T21047028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | affine group of R^n |
E518474
|
entity |
| Predicate | isFaithfulActionOn |
P9769
|
FINISHED |
| Object | R^n |
—
|
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: R^n | Statement: [affine group of R^n, isFaithfulActionOn, R^n]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFaithfulActionOn Context triple: [affine group of R^n, isFaithfulActionOn, R^n]
-
A.
hasFaithfulOfRite
Indicates that a religious body or authority has adherents who follow a specific liturgical rite.
-
B.
servesFaithfulOf
Indicates that one entity performs services or acts in a ministering or supportive role for those who are faithful to another entity.
-
C.
hasLayFaithful
Indicates that an entity (typically a religious organization or community) includes or is associated with lay faithful, i.e., non-ordained members of the faith.
-
D.
hasFaithfulCategory
Indicates that one entity is associated with a category functor that is faithful, i.e., it preserves distinct morphisms without identifying them.
-
E.
actsOn
chosen
Indicates that one entity performs an action that affects, targets, or is directed toward another entity.
- 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_69e0b50438e08190917e2538bb8bc034 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fcf4d26481908b639996500a8319 |
completed | April 21, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf6728881908a2a43a5c8804a2a |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:34 p.m.