Triple
T38644865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medic |
E938688
|
entity |
| Predicate | RestorationTargets |
P38451
|
FINISHED |
| Object | friendly units |
—
|
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: friendly units | Statement: [Medic, RestorationTargets, friendly units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RestorationTargets Context triple: [Medic, RestorationTargets, friendly units]
-
A.
restorationGoal
Indicates that an action or plan is intended to return something to a previous, original, or improved state or condition.
-
B.
restorationType
Indicates the specific kind or category of restoration applied to an entity, such as the method, scope, or approach used to return it to a prior or improved state.
-
C.
restorationProject
Indicates a project whose purpose is to repair, renew, or return something to a previous or improved condition.
-
D.
restorationUse
Indicates the use of something specifically for the purpose of restoring, repairing, or returning another entity to a previous or improved state.
-
E.
restorationFocus
chosen
Indicates that the primary attention or effort is directed toward repairing, renewing, or returning something to a previous or improved state.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:32 p.m.