Triple
T7489916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | t_P |
E176978
|
entity |
| Predicate | isFundamentalIn |
P74070
|
FINISHED |
| Object | Planck scale definitions |
—
|
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 scale definitions | Statement: [t_P, isFundamentalIn, Planck scale definitions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFundamentalIn Context triple: [t_P, isFundamentalIn, Planck scale definitions]
-
A.
isFundamental
Indicates that something is a basic, essential, or foundational element upon which other things depend or are built.
-
B.
isFeatureOf
Indicates that something functions as a characteristic, attribute, or component belonging to or describing another entity.
-
C.
isRootOf
Indicates that one entity is the root or origin point from which another entity directly or indirectly descends or is derived.
-
D.
hasBasisIn
chosen
Indicates that one entity is founded, derived, or justified on the grounds of another entity.
-
E.
isBaseFor
Indicates that one entity serves as the foundational support, starting point, or underlying basis upon which another entity is built, developed, or depends.
- 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_69c69f2583808190bd1a4936c42a5815 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f55bdb3481908653b46eafba011d |
completed | March 27, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c6f03eeaa88190a5215772ed05ee9f |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:43 p.m.