Triple
T33439559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marian apparitions of 1877 |
E856322
|
entity |
| Predicate | hasMainSeerAgeAtTime |
P2042
|
FINISHED |
| Object | 13 |
—
|
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: 13 | Statement: [Marian apparitions of 1877, hasMainSeerAgeAtTime, 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainSeerAgeAtTime Context triple: [Marian apparitions of 1877, hasMainSeerAgeAtTime, 13]
-
A.
hasOtherSeerAgeAtTime
Indicates that one entity has a recorded age of another seer at a specific point in time.
-
B.
hasAgeInMainTimeline
Indicates that an entity has a specific age value within the primary or canonical timeline of a narrative or system.
-
C.
hasApproximateUpperAge
Indicates that an entity is associated with an estimated or non-exact maximum age limit.
-
D.
hasApproximateEndAge
Indicates that an entity is associated with an estimated or imprecise age at which it ends, ceases, or is no longer applicable.
-
E.
hasAge
chosen
Indicates that an entity possesses a specific age value, typically expressed as a number of time units since its birth or creation.
- 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_69f34971b75881908be360bb041f003c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0117b6539c8190be7d231e891fe546 |
completed | May 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_6a011762f7ec8190afc884b92419d33f |
completed | May 10, 2026, 11:40 p.m. |
Created at: May 1, 2026, 1:37 a.m.