Triple
T38309535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regor (cut-down) |
E1033645
|
entity |
| Predicate | hasCoreName |
—
|
GENERATED |
| Object | Regor |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreName Context triple: [Regor (cut-down), hasCoreName, Regor]
-
A.
hasCore
Indicates that one entity possesses, contains, or is built around a central or most essential component represented by another entity.
-
B.
hasCoreValue
Indicates that an entity possesses or is characterized by a fundamental guiding principle or core belief.
-
C.
hasCoreClass
Indicates that an entity is associated with, or belongs to, a primary or fundamental class within a classification system.
-
D.
hasCoreFunction
Indicates that one entity serves as a primary or essential function or role of another entity.
-
E.
hasCurrentCoreCityName
chosen
Indicates that an entity is associated with its present or officially recognized core city name.
- F. None of above.
Provenance (1 batch)
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_69f76e132c408190969b3d35c04b87ae |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:30 p.m.