Triple
T4547344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copernican system |
E110077
|
entity |
| Predicate | adoptedGraduallyIn |
P9863
|
FINISHED |
| Object | Catholic countries |
—
|
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: Catholic countries | Statement: [Copernican system, adoptedGraduallyIn, Catholic countries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptedGraduallyIn Context triple: [Copernican system, adoptedGraduallyIn, Catholic countries]
-
A.
adoptedGraduallyBy
chosen
Indicates that one entity is taken up, accepted, or implemented by another entity in a slow, incremental, or phased manner over time.
-
B.
adoptedBy
Indicates that an entity has been taken in and legally or formally accepted as a child, member, or responsibility by another entity.
-
C.
adopted
Indicates that one entity has legally taken another (often a child or animal) into its family or care as a permanent member.
-
D.
adoptedInPlace
Indicates that an adoption event occurred within or is associated with a specific place or location.
-
E.
laterAdoptedBy
Indicates that one entity is adopted by another entity at a later point in time, after some prior state or relationship has already been established.
- 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_69bd4412524c8190be5bcc9ddee91848 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57f11f648190b20892cca6f617b1 |
completed | March 20, 2026, 2:21 p.m. |
| PD | Predicate disambiguation | batch_69bd5220e40481908ca2d7e2c43d8531 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:05 p.m.