Triple
T5008415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sagredo |
E112552
|
entity |
| Predicate | alignmentInDebate |
P50993
|
FINISHED |
| Object | sympathetic to Copernicanism |
—
|
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: sympathetic to Copernicanism | Statement: [Sagredo, alignmentInDebate, sympathetic to Copernicanism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alignmentInDebate Context triple: [Sagredo, alignmentInDebate, sympathetic to Copernicanism]
-
A.
fieldOfDebate
Indicates that something is the subject or domain around which a debate or argumentative discussion is centered.
-
B.
partOfDebate
Indicates that one entity is a component, segment, or participant within a larger debate or argumentative exchange.
-
C.
relatedToDebate
chosen
Indicates a relationship in which something is connected or relevant to a debate, discussion, or argumentative exchange.
-
D.
alignedAgainst
Indicates that two or more entities are united in opposition to a common target, side, or objective.
-
E.
keyFigureInDebate
Indicates that an entity plays a central, influential, or prominently recognized role in a particular debate or controversy.
- 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_69bd4433d0b08190877e83959ef40d81 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd730a7590819088ab8d49c5c88c2f |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714cbc448190aa53a8a83d768b64 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.