Triple
T31595151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Nilus the Younger |
E806199
|
entity |
| Predicate | roleAtGrottaferrata |
P45817
|
FINISHED |
| Object | first abbot |
—
|
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: first abbot | Statement: [Saint Nilus the Younger, roleAtGrottaferrata, first abbot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtGrottaferrata Context triple: [Saint Nilus the Younger, roleAtGrottaferrata, first abbot]
-
A.
roleInRome
Indicates that an entity holds or held a specific role, position, or function within the context of Rome or Roman society.
-
B.
roleInAttraction
chosen
Indicates the specific function or position an entity holds within the context of a particular attraction or point of interest.
-
C.
interactionWithRome
Indicates a relationship in which an entity engages in some form of contact, exchange, or involvement with Rome.
-
D.
roleAtA24
Indicates that an entity holds or held a specific role or position at the organization or project referred to as A24.
-
E.
roleInMonument
Indicates that an entity holds or held a specific role, function, or contribution in relation to a particular monument.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 30, 2026, 10:30 p.m.