Triple
T35074312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 9135 Lacaille |
E1011968
|
entity |
| Predicate | namedAfterCenturyOfActivity |
P1560
|
FINISHED |
| Object | 18th century |
—
|
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: 18th century | Statement: [9135 Lacaille, namedAfterCenturyOfActivity, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedAfterCenturyOfActivity Context triple: [9135 Lacaille, namedAfterCenturyOfActivity, 18th century]
-
A.
namedAfterCentury
Indicates that something is named after a specific century, typically reflecting that century’s time period or characteristics.
-
B.
activeInCentury
chosen
Indicates that an entity was active, influential, or operational during a specified century.
-
C.
celebratedSinceCentury
Indicates that a celebration, commemoration, or observance of something has been taking place continuously since a specified century.
-
D.
activeUntilCentury
Indicates that an entity remains active or in effect up to and including a specified century.
-
E.
notableFromCentury
Indicates that an entity is notably associated with, or best known from, a particular century.
- 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_69f76dd193108190af2528186f25b72a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: May 3, 2026, 4:01 p.m.