Triple
T11334907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marcia |
E268445
|
entity |
| Predicate | lifeInferredFrom |
P98570
|
FINISHED |
| Object | ancient literary sources |
—
|
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: ancient literary sources | Statement: [Marcia, lifeInferredFrom, ancient literary sources]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifeInferredFrom Context triple: [Marcia, lifeInferredFrom, ancient literary sources]
-
A.
livesAccordingTo
Indicates that an entity conducts its life or behavior in alignment with a specified principle, rule, belief system, or standard.
-
B.
lifeDetails
Indicates that additional information or specific aspects about an entity’s life (such as background, experiences, or personal history) are being described.
-
C.
living
Indicates that an entity is alive or currently exists in a living state.
-
D.
hasRoleInLifeOf
Indicates that one entity plays a particular role or function in the life or personal experience of another entity.
-
E.
lifeStatus
Indicates the current state of an entity’s existence, such as whether it is alive, dead, or in another defined life condition.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9ff62c88190a089dd84e2ac1d17 |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787afe5a48190b8af1a3e19529641 |
completed | April 9, 2026, 11:04 a.m. |
| PDg | Predicate description generation | batch_69d796d049e88190a9fd7508f477f541 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:33 p.m.