Triple
T28464778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arcesilaus |
E720259
|
entity |
| Predicate | viewOnAssent |
P178288
|
FINISHED |
| Object | recommended withholding assent |
—
|
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: recommended withholding assent | Statement: [Arcesilaus, viewOnAssent, recommended withholding assent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewOnAssent Context triple: [Arcesilaus, viewOnAssent, recommended withholding assent]
-
A.
viewOnConsent
Indicates that one entity is permitted to view another entity or its data only after obtaining explicit consent.
-
B.
viewOnConsensus
Indicates the stance or opinion an entity holds regarding a consensus or commonly agreed-upon position.
-
C.
viewOnAuthority
Indicates how an entity perceives, evaluates, or relates to authority, including attitudes toward obedience, legitimacy, and power structures.
-
D.
viewOnAssurance
Indicates a stance, opinion, or perspective that one entity holds regarding the assurance, reliability, or guarantee associated with another entity or process.
-
E.
viewOnPolicy
Indicates a stance, opinion, or perspective that an entity holds regarding a specific policy.
- F. None of above. chosen
Provenance (4 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_69f01a58a67c819097936d9e8da8d6e6 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70e854b9c8190a3416e2189e17742 |
completed | May 3, 2026, 8:59 a.m. |
Created at: April 28, 2026, 2:43 a.m.