Triple
T37565731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finduilas |
E933948
|
entity |
| Predicate | burialMoundTranslation |
P188292
|
FINISHED |
| Object | Mound of the Elf-maid |
—
|
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: Mound of the Elf-maid | Statement: [Finduilas, burialMoundTranslation, Mound of the Elf-maid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialMoundTranslation Context triple: [Finduilas, burialMoundTranslation, Mound of the Elf-maid]
-
A.
archaeologicalMoundName
Indicates the specific name assigned to an archaeological mound in which something is located, associated, or from which it originates.
-
B.
nearbyBurialMoundsAttributedTo
Indicates that one entity is located close to burial mounds that are believed or assigned to be associated with another entity.
-
C.
hasBurialMonumentType
Indicates that an entity is associated with a burial whose monument is of a specified type.
-
D.
burialComplexOf
Indicates that one entity is the burial complex associated with, containing, or dedicated to another entity (typically the person or group interred there).
-
E.
burialText
Indicates that a text is inscribed on, associated with, or used in connection with a burial or funerary context.
- F. None of above. chosen
Provenance (4 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_69f76ecb4acc8190b53f96d0b013e415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba61dff5081909fec88a7aeb0c8a1 |
completed | May 6, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69fba350e9a8819095893229d9643572 |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba61d2214819091ae6793bfefb1f0 |
completed | May 6, 2026, 8:35 p.m. |
Created at: May 3, 2026, 4:17 p.m.