Triple
T25828832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planck density |
E650603
|
entity |
| Predicate | isSometimesExpressedIn |
P87213
|
FINISHED |
| Object | Planck mass per Planck volume |
—
|
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: Planck mass per Planck volume | Statement: [Planck density, isSometimesExpressedIn, Planck mass per Planck volume]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSometimesExpressedIn Context triple: [Planck density, isSometimesExpressedIn, Planck mass per Planck volume]
-
A.
oftenExpressedAs
chosen
Indicates that one thing is frequently represented, stated, or manifested in the form of another.
-
B.
expressedDuring
Indicates that an action, state, or condition occurs or is manifested within a specified temporal interval or event.
-
C.
expresses
Indicates that one entity conveys, communicates, or articulates a thought, feeling, or idea through another medium or form.
-
D.
expressedOn
Indicates that something (such as a feature, marker, or characteristic) is present or manifested on a particular entity or surface.
-
E.
isSometimesUsedFor
Indicates that something serves a particular purpose or function on some occasions, but not consistently or exclusively.
- 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_69e7ab37438081908f1ccf6284839520 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6019807f08190bbeb8be744551fdf |
completed | May 2, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 7:37 a.m.