Triple
T4462425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pavlov's House |
E98285
|
entity |
| Predicate | frontLineStatus |
P2502
|
FINISHED |
| Object | front-line strongpoint |
—
|
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: front-line strongpoint | Statement: [Pavlov's House, frontLineStatus, front-line strongpoint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontLineStatus Context triple: [Pavlov's House, frontLineStatus, front-line strongpoint]
-
A.
frontLine
chosen
Indicates that an entity is positioned at or associated with the foremost or primary line of engagement, activity, or defense relative to others.
-
B.
frontLineLength
Indicates the total measured extent of the front line where opposing forces or boundaries directly face each other.
-
C.
frontLineReached
Indicates that an entity has arrived at or crossed into the designated front line or primary boundary of engagement.
-
D.
frontLineBetween
Indicates that a boundary or line of direct confrontation exists separating two opposing sides or regions.
-
E.
frontLineFeature
Indicates that the subject is a prominent or leading characteristic that stands out at the forefront relative to others.
- 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_69b3454a7c608190944f5455c8031d73 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3567716a4819092a5bc9732e74592 |
completed | March 13, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69b34f65f6448190abfadb2ae5658798 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:34 p.m.