Triple
T25750411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genesis |
E648455
|
entity |
| Predicate | scienceResult |
P21442
|
FINISHED |
| Object | constraints on solar and planetary formation 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: constraints on solar and planetary formation models | Statement: [Genesis, scienceResult, constraints on solar and planetary formation models]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scienceResult Context triple: [Genesis, scienceResult, constraints on solar and planetary formation models]
-
A.
researchOutcome
chosen
Indicates that an action, study, or investigation produces a specific result, finding, or conclusion.
-
B.
scienceReturn
Indicates that an action or process yields scientific data, findings, or value as its outcome.
-
C.
scientificResearch
Indicates that an entity conducts, participates in, or is the subject of systematic scientific investigation or study.
-
D.
nearbyScientificAchievement
Indicates that a scientific achievement occurs or exists in close spatial proximity to a specified reference point or entity.
-
E.
coResearcher
Indicates that two or more individuals collaborate as peers on the same research work or project.
- 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f600c18a14819081b5914dd3b0f9cf |
completed | May 2, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 22, 2026, 4:34 a.m.