Triple
T12069887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T-SAGE instrument |
E287394
|
entity |
| Predicate | testedPrinciple |
P33073
|
FINISHED |
| Object | weak equivalence principle |
—
|
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: weak equivalence principle | Statement: [T-SAGE instrument, testedPrinciple, weak equivalence principle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testedPrinciple Context triple: [T-SAGE instrument, testedPrinciple, weak equivalence principle]
-
A.
testsPrinciple
chosen
Indicates that an entity evaluates, examines, or challenges the validity or applicability of a principle.
-
B.
implementsPrinciple
Indicates that an entity applies, follows, or puts into practice a specified principle in its design, behavior, or operation.
-
C.
usesPrinciple
Indicates that one entity applies, relies on, or is based upon a particular principle in its functioning, reasoning, or design.
-
D.
eachPrincipleObservedOn
Indicates that every individual principle is observed, applied, or in effect on a specified occasion, context, or entity.
-
E.
testedFor
Indicates that an entity has been examined or analyzed to determine the presence, absence, or level of another specified entity or condition.
- 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_69d6ab4846e081908ee7bbd66a6d3459 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bda47c8190b94860b31df4a98c |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:48 p.m.