Triple
T4661789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lemaître–Tolman metric |
E102548
|
entity |
| Predicate | hasFreeFunction |
P56539
|
FINISHED |
| Object | mass function of radius |
—
|
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: mass function of radius | Statement: [Lemaître–Tolman metric, hasFreeFunction, mass function of radius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFreeFunction Context triple: [Lemaître–Tolman metric, hasFreeFunction, mass function of radius]
-
A.
usesFunction
Indicates that one entity employs, invokes, or relies on a particular function to perform an operation or achieve a result.
-
B.
containsFunction
chosen
Indicates that one entity includes, defines, or provides the implementation of a particular function.
-
C.
hasFreeZone
Indicates that an entity includes or is associated with a designated free zone area where special rules, privileges, or exemptions apply.
-
D.
hasHubFunction
Indicates that an entity serves as a central hub or coordinating point for certain activities, connections, or functions within a system.
-
E.
hasFunctionInComplex
Indicates that an entity performs a specific functional role within a larger molecular or structural complex.
- 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_69bd43d823288190952279faa0d1d066 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd632b7fb88190821f213620719d6b |
completed | March 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69bd62126b0c81909ba3f21b21e30d54 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:15 p.m.