Triple
T22785688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacinta de Jesus Marto |
E563958
|
entity |
| Predicate | reportedApparitionsIn |
P21320
|
FINISHED |
| Object | 1917 |
—
|
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: 1917 | Statement: [Jacinta de Jesus Marto, reportedApparitionsIn, 1917]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportedApparitionsIn Context triple: [Jacinta de Jesus Marto, reportedApparitionsIn, 1917]
-
A.
reportedApparitionEntity
chosen
Indicates that an entity has been reported or described as an apparition in some account or observation.
-
B.
apparitionWitnessCount
Indicates the number of distinct observers who witnessed a particular apparition event.
-
C.
reportedFor
Indicates that one entity has formally notified an authority or system about another entity’s behavior, condition, or status, typically to trigger review or action.
-
D.
associatedWithApparition
Indicates a relationship where something is linked or connected to an apparition, such as being caused by, accompanying, or characterizing that apparition.
-
E.
reportedAs
Indicates that one entity has been formally reported or flagged to another entity, typically as problematic, suspicious, or noteworthy.
- 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_69e2455500788190b4b33030461f3bbd |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17c30b4dc8190a5e23f4ce7feb300 |
completed | April 29, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:29 p.m.