Triple
T22936148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mare Fecunditatis |
E569588
|
entity |
| Predicate | olderUnitsAge |
P150320
|
FINISHED |
| Object | Nectarian |
—
|
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: Nectarian | Statement: [Mare Fecunditatis, olderUnitsAge, Nectarian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: olderUnitsAge Context triple: [Mare Fecunditatis, olderUnitsAge, Nectarian]
-
A.
olderComponent
Indicates that one component has existed or was created earlier in time than another component in the relationship.
-
B.
ageBased
Indicates a relationship or condition that depends on or is determined by the age of the entities involved.
-
C.
oldestAge
Indicates that the associated value represents the greatest (maximum) age within a given group, set, or context.
-
D.
ageSystem
Indicates a relationship where one entity specifies or uses a particular system or standard for expressing age (e.g., calendar system, counting convention, or age-measurement method) for another entity.
-
E.
mayBeAgedIn
Indicates that an entity has the potential or option to undergo an aging or maturation process in a specified medium, container, or environment.
- 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_69e24590862c8190858f180ad302adab |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1813608e48190922df7a5386dc391 |
completed | April 29, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:44 p.m.