Triple
T26946518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haifeng County |
E678657
|
entity |
| Predicate | revolutionaryBaseArea |
P99383
|
FINISHED |
| Object | Hai-Lu-Feng Soviet area |
—
|
NE NERFINISHED |
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: Hai-Lu-Feng Soviet area | Statement: [Haifeng County, revolutionaryBaseArea, Hai-Lu-Feng Soviet area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revolutionaryBaseArea Context triple: [Haifeng County, revolutionaryBaseArea, Hai-Lu-Feng Soviet area]
-
A.
liberatedArea
Indicates that a particular area has been freed from control, occupation, or domination by a previously prevailing power or force.
-
B.
rebelBase
chosen
Indicates a location that serves as a primary stronghold, headquarters, or operational center for a rebel or resistance group.
-
C.
servesAsTerritorialBaseFor
Indicates that a place or area functions as the primary territorial base or stronghold from which an entity operates or exerts influence.
-
D.
coreAreaOf
Indicates that one entity is the central, primary, or most important area or domain of focus for another entity.
-
E.
coreZoneArea
Indicates the area or spatial extent of a designated core zone within a larger region or system.
- 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f620858a4081909de8afda69398553 |
completed | May 2, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 6:21 a.m.