Triple
T65852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FLRW cosmological models |
E1311
|
entity |
| Predicate | compatibleWith |
P203
|
FINISHED |
| Object | cosmic microwave background isotropy |
—
|
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: cosmic microwave background isotropy | Statement: [FLRW cosmological models, compatibleWith, cosmic microwave background isotropy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compatibleWith Context triple: [FLRW cosmological models, compatibleWith, cosmic microwave background isotropy]
-
A.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
B.
competesWith
Indicates that two entities are in rivalry or opposition, each striving to outperform or gain advantage over the other in the same domain or objective.
-
C.
supportsFeature
chosen
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
D.
availableAs
Indicates that one entity can be used, accessed, or offered in the form, role, or capacity of another entity.
-
E.
canAlsoBe
Indicates that something has an additional possible state, role, or classification beyond its primary one.
- 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a2516eda54819090f5c14384d4eab1 |
completed | Feb. 28, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_69a24ea5c140819080409a968c8d2ce8 |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.