Triple
T20530507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GCl 104 |
E504053
|
entity |
| Predicate | hasCentralConcentration |
P61029
|
FINISHED |
| Object | strong |
—
|
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: strong | Statement: [GCl 104, hasCentralConcentration, strong]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralConcentration Context triple: [GCl 104, hasCentralConcentration, strong]
-
A.
hasCentralDensity
chosen
Indicates that an entity possesses a specified value for its density at the central or core region.
-
B.
hasCentralIntensity
Indicates that something possesses a specific value or measure of intensity at its central point or core region.
-
C.
hasCentralOrgan
Indicates that an entity possesses a primary or main organ that serves as a central functional or structural component.
-
D.
hasCentralRegion
Indicates that an entity possesses or is associated with a primary or central area within its overall structure or domain.
-
E.
hasCentralAct
Indicates that an entity includes or is characterized by a primary or most important action, event, or operation at its core.
- 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_69e0b4b3a6e08190ae663701f50fab8e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a069edf88190835a9c392c990c55 |
completed | April 20, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:37 a.m.