Triple
T1564815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planck time |
E33407
|
entity |
| Predicate | isShortestMeaningfulIntervalIn |
P4229
|
FINISHED |
| Object | current physical theories |
—
|
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: current physical theories | Statement: [Planck time, isShortestMeaningfulIntervalIn, current physical theories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isShortestMeaningfulIntervalIn Context triple: [Planck time, isShortestMeaningfulIntervalIn, current physical theories]
-
A.
invariantInterval
Indicates that a certain interval or range remains unchanged or constant under a specified transformation or set of conditions.
-
B.
timePeriodWithin
Indicates that one time period is entirely contained within the bounds of another time period.
-
C.
isMinimumWhen
chosen
Indicates that a value or state is at its smallest or least level precisely under certain specified conditions or circumstances.
-
D.
isShortLived
Indicates that an entity exists or remains in a particular state for only a brief or limited period of time.
-
E.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
- 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_69a885f11b048190935025a035302715 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90fccd4b48190a44012888a00af7f |
completed | March 5, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69a907b872f0819096b3df6ad502c63e |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:27 p.m.