Triple
T9130625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Survivor Tree |
E219075
|
entity |
| Predicate | conditionAtDiscovery |
P24157
|
FINISHED |
| Object | badly damaged |
—
|
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: badly damaged | Statement: [Survivor Tree, conditionAtDiscovery, badly damaged]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conditionAtDiscovery Context triple: [Survivor Tree, conditionAtDiscovery, badly damaged]
-
A.
conditionStudied
Indicates that a particular condition (e.g., disease, state, or circumstance) is the focus of study or investigation in a given context.
-
B.
presentCondition
chosen
Indicates that an entity currently has or exhibits a particular state, situation, or condition.
-
C.
appointmentCondition
Indicates the specific terms, requirements, or circumstances that must be met or that apply for an appointment to be scheduled, valid, or carried out.
-
D.
conditionForRecognition
Indicates that one entity specifies the requirement or circumstance under which another entity is acknowledged, accepted, or officially recognized.
-
E.
captureCondition
Indicates the specific circumstances or criteria under which a capture event or action is triggered or considered valid.
- 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_69ca83debfc0819095800583e97ab10f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8cdafb48190be5e62b15779d771 |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc6601d77881908299d58db6e64937 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:18 p.m.