Triple
T11350117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bernadette Soubirous |
E268818
|
entity |
| Predicate | numberOfApparitionsReported |
P42152
|
FINISHED |
| Object | 18 |
—
|
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: 18 | Statement: [Bernadette Soubirous, numberOfApparitionsReported, 18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfApparitionsReported Context triple: [Bernadette Soubirous, numberOfApparitionsReported, 18]
-
A.
resultsReportedAs
Indicates that the outcomes or findings of an activity, process, or evaluation are communicated or documented in a specified form, format, or medium.
-
B.
numberOfCounts
chosen
Indicates the total quantity or tally of discrete occurrences, items, or instances associated with an entity or event.
-
C.
reportsUsedBy
Indicates that a report is utilized or referenced by another entity (such as a user, system, or process).
-
D.
numberOfInstances
Indicates the quantity or count of distinct occurrences or instances associated with a given entity or context.
-
E.
areCountedBy
Indicates that one entity serves as the counting mechanism, record, or process by which the quantity of another entity is determined.
- 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_69d6aacbe18081909e5fadb50082dd96 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d80148e2048190a716b515d78efdd1 |
completed | April 9, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69d7e6f8aeb4819080476f16a69b2ee3 |
completed | April 9, 2026, 5:50 p.m. |
Created at: April 8, 2026, 9:33 p.m.