Triple
T33839609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imbrian period |
E867322
|
entity |
| Predicate | hasKeyBasin |
P188458
|
FINISHED |
| Object | Imbrium basin |
—
|
NE NERFINISHED |
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: Imbrium basin | Statement: [Imbrian period, hasKeyBasin, Imbrium basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyBasin Context triple: [Imbrian period, hasKeyBasin, Imbrium basin]
-
A.
hasBasinNamed
Indicates that an entity possesses or is associated with a basin that has a specified name.
-
B.
hasBasinFunction
Indicates that something serves the role or performs the function of a basin, such as collecting, holding, or draining water or other substances.
-
C.
hasWaterBasins
Indicates that one entity possesses, contains, or includes one or more water basins in relation to another entity.
-
D.
basinFor
Indicates that something serves as a basin or receptacle specifically intended for collecting, holding, or draining another entity.
-
E.
hasSettlementInBasin
Indicates that a settlement is located within the geographic area of a specific basin.
- F. None of above. chosen
Provenance (4 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba789c1188190973a919bfe2871f3 |
completed | May 6, 2026, 8:41 p.m. |
Created at: May 1, 2026, 1:47 a.m.