Triple
T26588733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broad Mountain plateau |
E667286
|
entity |
| Predicate | hostsCommunity |
P164845
|
FINISHED |
| Object | Frackville |
—
|
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: Frackville | Statement: [Broad Mountain plateau, hostsCommunity, Frackville]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostsCommunity Context triple: [Broad Mountain plateau, hostsCommunity, Frackville]
-
A.
hostsBuilding
Indicates that one entity serves as the location or site that accommodates or contains a particular building.
-
B.
hostFamily
Indicates that one entity serves as a host family, providing accommodation, care, or support to another entity, typically for a temporary or exchange-based stay.
-
C.
hostGroups
Indicates a grouping relationship where a host belongs to or is associated with one or more defined host groups.
-
D.
hostsUnit
Indicates that one entity serves as the location or container in which another unit is situated, operates, or is organized.
-
E.
hostNOC
Indicates that one entity operates as the Network Operations Center (NOC) responsible for monitoring, managing, or supporting another entity’s network or services.
- F. None of above. chosen
Provenance (4 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f650fc44e48190bc0e0a935eac62a6 |
completed | May 2, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f650c466b881908954e43bfebae8a4 |
completed | May 2, 2026, 7:30 p.m. |
Created at: April 27, 2026, 2:07 a.m.