Triple

T3285321
Position Surface form Disambiguated ID Type / Status
Subject Carmen E68965 entity
Predicate healthStatus P33305 FINISHED
Object fragile health 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: fragile health | Statement: [Carmen, healthStatus, fragile health]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: healthStatus
Context triple: [Carmen, healthStatus, fragile health]
  • A. healthIndicator chosen
    Indicates a measure or signal that reflects the health status or condition of an entity.
  • B. healthProxy
    Indicates that one entity is authorized to make health-related or medical decisions on behalf of another entity.
  • C. publicHealthResponse
    Indicates actions and measures taken by authorities or organizations to prevent, control, or mitigate health threats within a population.
  • D. hasHealthConcern
    Indicates that an entity has a specific health-related issue, condition, or concern associated with it.
  • E. healthEffect
    Indicates the impact or consequence that one entity has on the health or well-being of another.
  • 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_69ad859c463481909ca4be267336c290 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb03918c48190987d7cfd3bda9716 completed March 8, 2026, 5:22 p.m.
PD Predicate disambiguation batch_69ada421fadc8190b7c7d3c8afd20061 completed March 8, 2026, 4:30 p.m.
Created at: March 8, 2026, 3:10 p.m.