Triple
T29120780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Crunch scenario |
E737174
|
entity |
| Predicate | timeSymmetryWith |
P47525
|
FINISHED |
| Object | Big Bang in some models |
—
|
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: Big Bang in some models | Statement: [Big Crunch scenario, timeSymmetryWith, Big Bang in some models]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeSymmetryWith Context triple: [Big Crunch scenario, timeSymmetryWith, Big Bang in some models]
-
A.
timeSymmetry
chosen
Indicates that a process or relationship remains valid and unchanged when the direction of time is reversed.
-
B.
testsSymmetry
Indicates that one entity evaluates or verifies whether a relationship or property holds identically in both directions between two entities.
-
C.
symmetryOf
Indicates that one entity is the symmetry counterpart or symmetric form of another entity, typically related by a specific symmetry operation or transformation.
-
D.
isHomogeneousInTime
Indicates that the relationship or property remains uniform and unchanged over time.
-
E.
timePeriodReflected
Indicates that one entity represents or corresponds to the time period associated with another entity.
- 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f661f3e9d48190bea96aeb602ab631 |
completed | May 2, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 11:25 a.m.