Triple
T8362793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viscount St Alban |
E197049
|
entity |
| Predicate | titleHolderMovement |
P82304
|
FINISHED |
| Object | Renaissance humanism |
—
|
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: Renaissance humanism | Statement: [Viscount St Alban, titleHolderMovement, Renaissance humanism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHolderMovement Context triple: [Viscount St Alban, titleHolderMovement, Renaissance humanism]
-
A.
titleHolderDuring
Indicates that one entity holds a specific title or position during a defined time period in relation to another entity.
-
B.
titleHolderIs
Indicates that one entity currently holds or possesses a specific title associated with another entity.
-
C.
titleHolderUnder
Indicates that one entity holds a title, position, or rank under the authority, jurisdiction, or hierarchy of another entity.
-
D.
titleHolderSide
Indicates which side, party, or competitor currently holds a particular title in a contest, match, or competition.
-
E.
titleHolderIsUsually
Indicates that an entity serving as a title holder is typically or most commonly a particular type or category of entity.
- 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_69ca82f2dbe48190aba982e75a0d94de |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80768b208190a5f6c9e6cb6e7f30 |
completed | March 31, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69cb70ca25548190b0f90c5384e3fb3c |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d823b08190a54fadb50660cda5 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 6 p.m.