Triple
T29749570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mountain troops |
E752855
|
entity |
| Predicate | faceChallenge |
P3326
|
FINISHED |
| Object | logistical supply in mountains |
—
|
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: logistical supply in mountains | Statement: [Mountain troops, faceChallenge, logistical supply in mountains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: faceChallenge Context triple: [Mountain troops, faceChallenge, logistical supply in mountains]
-
A.
facesChallenge
chosen
Indicates that an entity is confronted with a difficulty, obstacle, or demanding situation that must be dealt with or overcome.
-
B.
faceResemblance
Indicates that one entity’s facial appearance is similar to or resembles that of another entity.
-
C.
hasFacialProfile
Indicates that an entity possesses a specific facial profile or configuration of facial features.
-
D.
faceVisibility
Indicates that one entity’s face is visible to another entity or from a particular viewpoint.
-
E.
faceValueType
Indicates the type or category of a financial instrument’s face (nominal) value, such as how that value is defined or represented.
- 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_69f0d62c84cc8190846f80ae04fdf8ec |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6736a13f08190b9695bb8796e0aec |
completed | May 2, 2026, 9:58 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 7:53 p.m.