Triple
T9564536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planck volume |
E230756
|
entity |
| Predicate | conceptRole |
P34667
|
FINISHED |
| Object | natural unit of 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: natural unit of volume | Statement: [Planck volume, conceptRole, natural unit of volume]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conceptRole Context triple: [Planck volume, conceptRole, natural unit of volume]
-
A.
conceptualRole
chosen
Indicates the functional or semantic role that one concept plays in relation to another within a conceptual structure or system.
-
B.
notationRole
Indicates a role or function that an entity plays specifically within a system of notation or symbolic representation.
-
C.
namedPersonRole
Indicates that a person is identified by name as holding a specific role or position in a given context.
-
D.
overarchingEntityRole
Indicates that one entity holds a broad, high-level role or responsibility that spans across or governs multiple other entities or activities.
-
E.
role
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
- 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_69ca847e53a88190a60eed7e02257f10 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd996a01b081908e2782f41520f73d |
completed | April 1, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69ccd594d0ac8190a81bc11a3a538167 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:04 p.m.