Triple
T20774925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capricorn |
E511330
|
entity |
| Predicate | broughtIntoWorldBy |
P41668
|
FINISHED |
| Object | Silvertongue’s reading |
—
|
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: Silvertongue’s reading | Statement: [Capricorn, broughtIntoWorldBy, Silvertongue’s reading]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broughtIntoWorldBy Context triple: [Capricorn, broughtIntoWorldBy, Silvertongue’s reading]
-
A.
creatorOfInhabitants
Indicates that an entity is the creator or originator of the beings or inhabitants of another entity (such as a place, world, or domain).
-
B.
wasBornInto
Indicates that an entity entered existence as a member of a particular family, social group, or circumstance at birth.
-
C.
createdInUniverseBy
chosen
Indicates that something was brought into existence within a particular fictional or conceptual universe by a specific creator or originating agent.
-
D.
gaveBirthTo
Indicates that one entity is the biological parent who delivered another entity as offspring.
-
E.
willBeBornAs
Indicates that an entity is predicted or destined to come into existence in the future as a particular individual or form.
- 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_69e0b4cac7a48190a715cb3d545df2b4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c26a39bc81909ca5d102056d8586 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:37 p.m.