Triple
T20161451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GCl 111 |
E491712
|
entity |
| Predicate | coreAppearance |
P138895
|
FINISHED |
| Object | loose, not strongly concentrated |
—
|
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: loose, not strongly concentrated | Statement: [GCl 111, coreAppearance, loose, not strongly concentrated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreAppearance Context triple: [GCl 111, coreAppearance, loose, not strongly concentrated]
-
A.
publicAppearance
Indicates that an entity participates in or is present at an event or situation that is open or visible to the general public.
-
B.
platformAppearance
Indicates how an entity is visually presented or styled on a particular platform or interface.
-
C.
primaryAppearance
Indicates that the referenced entity is the main or most prominent visual or representational form in which another entity is typically depicted or recognized.
-
D.
coreDesignStyle
Indicates the primary or defining design style that characterizes an entity’s overall aesthetic or structural approach.
-
E.
adaptationAppearance
Indicates that one entity appears or is depicted in an adaptation of another entity (such as a work being represented in a derived or reinterpreted version).
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e667e43940819080f6a0b7331aaab0 |
completed | April 20, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56700b1a08190ace53cf95827d72d |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:34 p.m.