Triple
T31636138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | causal dynamical triangulations |
E807317
|
entity |
| Predicate | usesBuildingBlocks |
P173731
|
FINISHED |
| Object | simplices |
—
|
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: simplices | Statement: [causal dynamical triangulations, usesBuildingBlocks, simplices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBuildingBlocks Context triple: [causal dynamical triangulations, usesBuildingBlocks, simplices]
-
A.
usesBuildingBlock
chosen
Indicates that one entity constructs, composes, or implements itself using another entity as a fundamental component or module.
-
B.
usesBuilding
Indicates that one entity makes use of, occupies, or operates within a particular building.
-
C.
usedOnBuildingOf
Indicates that something is applied to, installed on, or otherwise utilized on the structure of a particular building.
-
D.
containsBuilding
Indicates that one location or area includes a building within its boundaries.
-
E.
hasBuildingFrom
Indicates a relationship where a location or site possesses or includes a building that originates from, or was constructed in, a specified time period, source, or 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_69f348d892948190915f8facacb9568c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 30, 2026, 10:47 p.m.