Triple
T8684950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universe |
E206133
|
entity |
| Predicate | obeyed |
P4454
|
FINISHED |
| Object | general relativity on large scales |
—
|
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: general relativity on large scales | Statement: [Universe, obeyed, general relativity on large scales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: obeyed Context triple: [Universe, obeyed, general relativity on large scales]
-
A.
obeysLaw
chosen
Indicates that an entity follows, complies with, or acts in accordance with a specified law or set of laws.
-
B.
thenObeyedCommand
Indicates that one entity subsequently complied with or carried out a command issued by another entity.
-
C.
hasSpecialVowOfObedienceRegarding
Indicates that one entity is bound by a distinct or additional vow to obey the authority, directives, or will of another specific entity.
-
D.
obeysStatistics
Indicates that one entity’s behavior or outcomes conform to, follow, or are governed by statistical laws or patterns.
-
E.
followsWillOf
Indicates that one entity acts in accordance with, or submits its decisions and behavior to, the intentions, desires, or directives of 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_69ca835379688190aa06b9d98e684d58 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4aeae740819099093906ccc5f640 |
completed | March 31, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69cc4569f9048190b9c86b4c81103d35 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:32 p.m.