Triple
T25677060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GF(p^m) |
E643835
|
entity |
| Predicate | traceMapTo |
P158982
|
FINISHED |
| Object | GF(p) |
—
|
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: GF(p) | Statement: [GF(p^m), traceMapTo, GF(p)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traceMapTo Context triple: [GF(p^m), traceMapTo, GF(p)]
-
A.
traceOf
Indicates that one entity is a remaining sign, mark, or residual evidence of the presence, existence, or action of another entity.
-
B.
tracesTo
Indicates a relationship where one item can be followed or linked back as the origin, source, or cause of another.
-
C.
traceWithRespectTo
Indicates that one entity records, follows, or monitors the behavior, changes, or effects of another entity relative to a specified reference or context.
-
D.
traceProperty
Indicates that a property or attribute of an entity is being tracked, recorded, or monitored over time or through a process.
-
E.
trace
Indicates following or mapping the path, origin, or development of something step by step through evidence or markers.
- 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_69e77e7f69808190ad27df1006f6037a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fb3712cc8190b6e851960cc7c9e9 |
completed | May 2, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 7:40 p.m.