Triple
T33900008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | α Aquarii |
E869019
|
entity |
| Predicate | hasApproxAge_years |
P174399
|
FINISHED |
| Object | tens of millions |
—
|
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: tens of millions | Statement: [α Aquarii, hasApproxAge_years, tens of millions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproxAge_years Context triple: [α Aquarii, hasApproxAge_years, tens of millions]
-
A.
hasApproximateUpperAge
Indicates that an entity is associated with an estimated or non-exact maximum age limit.
-
B.
hasApproximateAgeRange
Indicates that one entity is associated with another entity representing an estimated or non-exact span of ages.
-
C.
hasAge
Indicates that an entity possesses a specific age value, typically expressed as a number of time units since its birth or creation.
-
D.
estimatedAgeYears
chosen
Indicates the approximate number of years assigned as an entity’s age based on estimation rather than exact measurement.
-
E.
containsAge
Indicates that one entity includes or specifies the age value or age-related information of another entity.
- 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_69f34997703c8190866b1d404bce531f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 1, 2026, 1:48 a.m.