Triple
T28386519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Congregation of Christian Brothers |
E719032
|
entity |
| Predicate | hasNotablePresenceIn |
P43156
|
FINISHED |
| Object | Ireland |
—
|
NE NERFINISHED |
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: Ireland | Statement: [Congregation of Christian Brothers, hasNotablePresenceIn, Ireland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotablePresenceIn Context triple: [Congregation of Christian Brothers, hasNotablePresenceIn, Ireland]
-
A.
notablePresence
chosen
Indicates that an entity has a significant or prominent presence in relation to another entity, context, or domain.
-
B.
hasLargePresenceIn
Indicates that an entity maintains a significant or dominant level of activity, influence, or representation within a specified location, domain, or context.
-
C.
hasMinorPresenceIn
Indicates that an entity is present or active in a location, context, or domain, but only to a small or limited extent.
-
D.
hasNotableRoleIn
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
-
E.
hasHumanPresence
Indicates that humans are physically present in or occupying a given location, object, or context.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69ff255b84788190a94682f4efe1d0b8 |
completed | May 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69ff24f3ab108190bb017a656cff3d82 |
completed | May 9, 2026, 12:13 p.m. |
Created at: April 28, 2026, 1:10 a.m.