Triple
T10501735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genesis Rock |
E247687
|
entity |
| Predicate | usedInStudyOf |
P24615
|
FINISHED |
| Object | lunar crust formation |
—
|
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: lunar crust formation | Statement: [Genesis Rock, usedInStudyOf, lunar crust formation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInStudyOf Context triple: [Genesis Rock, usedInStudyOf, lunar crust formation]
-
A.
isStudiedUsing
Indicates that something serves as the method, tool, or approach by which something else is examined, analyzed, or researched.
-
B.
isSubjectOfStudy
Indicates that an entity is the focus or topic being examined, researched, or analyzed in a study or investigation.
-
C.
hasResearchUse
chosen
Indicates that an entity is used for, or associated with, conducting research activities or purposes.
-
D.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
E.
studiedWithin
Indicates that one entity pursued studies or academic work within the scope, context, or boundaries defined by another entity (such as an institution, program, or field).
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5099b797c8190a94803fa94eb6981 |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8e24ac8190912c9f11b8bd3084 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:25 p.m.